0s autopkgtest: DBG: testbed init 0s autopkgtest [23:58:12]: starting date and time: 2025-02-15 23:58:12+0000 0s autopkgtest [23:58:12]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [23:58:12]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.5ogut_s7/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:glibc,src:iproute2,src:php-twig,src:postgresql-17,src:postgresql-common,src:roundcube --apt-upgrade libfprint --debug --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=glibc/2.41-1ubuntu1 iproute2/6.13.0-1ubuntu1 php-twig/3.19.0-1 postgresql-17/17.3-2 postgresql-common/273 roundcube/1.6.10+dfsg-1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-s390x-13.secgroup --name adt-plucky-s390x-libfprint-20250215-235811-juju-7f2275-prod-proposed-migration-environment-15-9222da39-3d71-44cd-acdf-2d32eb48f048 --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/ 0s autopkgtest: DBG: got reply from testbed: ok 0s autopkgtest: DBG: testbed open, scratch=None 0s autopkgtest: DBG: sending command to testbed: open 95s autopkgtest: DBG: got reply from testbed: ok /tmp/autopkgtest.DF7m5L 95s autopkgtest: DBG: sending command to testbed: print-execute-command 95s autopkgtest: DBG: got reply from testbed: ok /tmp/autopkgtest-ssh.hxj7q2b1/runcmd 95s autopkgtest: DBG: sending command to testbed: capabilities 95s autopkgtest: DBG: got reply from testbed: ok isolation-machine reboot revert-full-system suggested-normal-user=ubuntu revert root-on-testbed 95s autopkgtest: DBG: testbed capabilities: ['isolation-machine', 'reboot', 'revert-full-system', 'suggested-normal-user=ubuntu', 'revert', 'root-on-testbed', 'has_internet'] 95s autopkgtest: DBG: testbed command ['mkdir', '-p', '/tmp/autopkgtest.DF7m5L'], kind short, sout raw, serr pipe, env [] 95s autopkgtest: DBG: testbed command exited with code 0 95s autopkgtest: DBG: sending command to testbed: copydown /home/ubuntu/autopkgtest/lib/in-testbed/wrapper.sh /tmp/autopkgtest.DF7m5L/wrapper.sh 95s autopkgtest: DBG: got reply from testbed: ok 95s autopkgtest: DBG: testbed command ['chmod', '-R', '0755', '--', '/tmp/autopkgtest.DF7m5L/wrapper.sh'], kind short, sout raw, serr pipe, env [] 96s autopkgtest: DBG: testbed command exited with code 0 96s autopkgtest: DBG: testbed command ['dpkg', '--print-architecture'], kind short, sout pipe, serr pipe, env [] 96s autopkgtest: DBG: testbed command exited with code 0 96s autopkgtest [23:59:48]: testbed dpkg architecture: s390x 96s autopkgtest: DBG: testbed command ['dpkg-query', '-W', '-f', '${Version}', 'apt'], kind short, sout pipe, serr pipe, env [] 96s autopkgtest: DBG: testbed command exited with code 0 96s autopkgtest [23:59:48]: testbed apt version: 2.9.28 96s autopkgtest: DBG: testbed command ['sh', '-ec', 'command -v eatmydata'], kind short, sout pipe, serr pipe, env [] 96s autopkgtest: DBG: testbed command exited with code 0 96s autopkgtest: DBG: testbed has eatmydata 96s autopkgtest: DBG: testbed command ['mkdir', '-p', '/etc/apt/preferences.d'], kind short, sout raw, serr pipe, env [] 96s autopkgtest: DBG: testbed command exited with code 0 96s autopkgtest [23:59:48]: @@@@@@@@@@@@@@@@@@@@ test bed setup 96s autopkgtest: DBG: testbed command ['sh', '-ec', '#!/bin/sh\n# Copyright © 2006-2018 Canonical Ltd.\n# Copyright © 2015-2017 Martin Pitt\n# Copyright © 2017 Steve Langasek\n# Copyright © 2017-2022 Paul Gevers\n# Copyright © 2018 Simon McVittie\n# SPDX-License-Identifier: GPL-2.0-or-later\n\n# This script returns the first suite found in apt sources. We can\'t just rely\n# on /etc/os-release because it doesn\'t allow to distinguish between Debian\n# unstable and testing.\n#\n# This release detection logic should be kept in sync with similar code in the\n# setup-testbed script.\n#\n# For more information on APT data sources see sources.list(5).\n\n# Usage $0\n\nset -eux\n\ndistro=UNKNOWN\nif [ -r /etc/os-release ]; then\n # shellcheck disable=SC1091\n distro=$(. /etc/os-release && echo "${ID:-$distro}")\nfi\n\n# Try guessing the default release from deb822-style format sources.\n#\n# While not mandatory, APT upstream expects distros to follow the\n# .sources naming pattern for the default deb822 sources.\napt_sources="/etc/apt/sources.list.d/$distro.sources"\nif [ -r "$apt_sources" ]; then\n release=$(sed -En \'s/^Suites:\\s*(\\w+).*/\\1/Ip\' "$apt_sources" | head -n1)\n [ -n "$release" ] && echo "$release" && exit\nfi\n\n# Try guessing the default release from one-line-style format sources.\napt_sources=/etc/apt/sources.list\nif [ -r "$apt_sources" ]; then\n release=$(sed -En \'/^(deb|deb-src) +(\\[.*\\] *)?(http|https|file):/ { s/\\[.*\\] +//; s/^[^ ]+ +[^ ]* +([^ ]+) +.*$/\\1/p }\' "$apt_sources" | head -n1)\n [ -n "$release" ] && echo "$release" && exit\nfi\n\n# Could not guess the default release\necho "Could not guess the default release from the APT sources." >&2\nexit 1\n'], kind short, sout pipe, serr pipe, env [] 96s autopkgtest: DBG: testbed command exited with code 0 96s autopkgtest [23:59:48]: testbed release detected to be: None 96s autopkgtest: DBG: testbed command ['sh', '-ec', '#!/bin/sh\n# SPDX-License-Identifier: GPL-2.0-or-later\n\n# This script returns the list of configured "deb" sources in one-line-style\n# source lists (/etc/apt/sources.list, /etc/apt/sources.list.d/*.list).\n# See sources.list(5) for more information on the APT source list formats.\n#\n# This script takes no arguments.\n\nset -eu\n\n# grep(1) returns 1 if no lines were selected from the input files, which\n# can happen if there are .list files, but they contain no "deb" entries.\n# We don\'t want to fail in this case, hence the "|| true", which we put\n# in a subshell because we want it to affect only the grep invocation.\n{\n if [ -f /etc/apt/sources.list ]; then\n printf \'%s\\0\' /etc/apt/sources.list\n fi\n if [ -d /etc/apt/sources.list.d ]; then\n find /etc/apt/sources.list.d -maxdepth 1 -type f -regex \'.*/[a-zA-Z0-9_.-]+\\.list\' -print0 \\\n | LC_ALL=C sort --zero-terminated\n fi\n} | xargs -0 --no-run-if-empty -- sh -c \'grep -h "^deb " "$@" || true\' "$(basename "$0")"\n'], kind short, sout pipe, serr pipe, env [] 97s autopkgtest: DBG: testbed command exited with code 0 97s autopkgtest: DBG: testbed command ['sh', '-ec', '#!/bin/sh\n# SPDX-License-Identifier: GPL-2.0-or-later\n\n# This script returns the list of configured sources in deb822-style source\n# lists (/etc/apt/sources.list.d/*.sources). Sources are not stripped out of\n# comments, extra blank lines or similar: the output of this script is meant to\n# be consumed by a deb822 parser that is able to correctly handle those.\n# See sources.list(5) for more information on the APT source list formats.\n#\n# This script takes no arguments.\n\nset -eu\n\n# Awk concatenates files making sure stanzas from separate files are separated\n# by a blank line, even if there are no newlines at EOF in the .sources files.\nif [ -d /etc/apt/sources.list.d ]; then\n find /etc/apt/sources.list.d -maxdepth 1 -type f -regex \'.*/[a-zA-Z0-9_.-]+\\.sources\' -print0 \\\n | LC_ALL=C sort --zero-terminated \\\n | xargs -0 --no-run-if-empty -- awk \'FNR == 1 && NR != 1 { print "" } { print }\'\nfi\n'], kind short, sout pipe, serr pipe, env [] 97s autopkgtest: DBG: testbed command exited with code 0 97s autopkgtest: DBG: adding APT source: Types: deb deb-src 97s URIs: http://ftpmaster.internal/ubuntu/ 97s Suites: plucky-proposed 97s Components: main restricted universe multiverse 97s Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg 97s autopkgtest: DBG: testbed command ['sh', '-ec', '"$@" >> "/etc/apt/sources.list.d/autopkgtest-add-apt-release-plucky-proposed.sources"', 'add_apt_source', 'printf', '%s\\n', 'Types: deb deb-src\nURIs: http://ftpmaster.internal/ubuntu/\nSuites: plucky-proposed\nComponents: main restricted universe multiverse\nSigned-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg\n'], kind short, sout raw, serr pipe, env [] 97s autopkgtest: DBG: testbed command exited with code 0 97s autopkgtest: DBG: adding APT preference to autopkgtest-zz-plucky-proposed-baseline.pref: 97s Package: * 97s Pin: release plucky-proposed 97s Pin-Priority: 500 97s autopkgtest: DBG: testbed command ['sh', '-ec', '"$@" > "/etc/apt/preferences.d/autopkgtest-zz-plucky-proposed-baseline.pref"', 'add_apt_preference', 'printf', '%s\\n', 'Package: *\nPin: release plucky-proposed\nPin-Priority: 500'], kind short, sout raw, serr pipe, env [] 97s autopkgtest: DBG: testbed command exited with code 0 97s autopkgtest [23:59:49]: updating testbed package index (apt update) 97s autopkgtest: DBG: testbed command ['/bin/sh', '-ec', '"$@" 3>&2 2>&1', 'run_apt_command', '/usr/bin/eatmydata', 'apt-get', '--quiet', '--assume-yes', '-o=APT::Status-Fd=3', '-o=APT::Install-Recommends=false', '-o=Dpkg::Options::=--force-confnew', '-o=Debug::pkgProblemResolver=true', 'update'], kind install, sout raw, serr pipe, env ['DEBIAN_FRONTEND=noninteractive', 'APT_LISTBUGS_FRONTEND=none', 'APT_LISTCHANGES_FRONTEND=none'] 97s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [110 kB] 98s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 98s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 98s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 98s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [13.1 kB] 98s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [3120 B] 98s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [74.3 kB] 98s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [828 kB] 98s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [163 kB] 98s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [760 B] 98s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [876 kB] 98s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [3740 B] 98s Fetched 2073 kB in 1s (2136 kB/s) 99s Reading package lists... 99s autopkgtest: DBG: testbed command exited with code 0 99s autopkgtest: DBG: adding APT preference to autopkgtest-plucky-proposed.pref: 99s Package: * 99s Pin: release plucky-proposed 99s Pin-Priority: 100 99s 99s Package: src:glibc:any src:iproute2:any src:php-twig:any src:postgresql-17:any src:postgresql-common:any src:roundcube:any 99s Pin: release plucky-proposed 99s Pin-Priority: 995 99s autopkgtest: DBG: testbed command ['sh', '-ec', '"$@" > "/etc/apt/preferences.d/autopkgtest-plucky-proposed.pref"', 'add_apt_preference', 'printf', '%s\\n', 'Package: *\nPin: release plucky-proposed\nPin-Priority: 100\n\nPackage: src:glibc:any src:iproute2:any src:php-twig:any src:postgresql-17:any src:postgresql-common:any src:roundcube:any\nPin: release plucky-proposed\nPin-Priority: 995'], kind short, sout raw, serr pipe, env [] 99s autopkgtest: DBG: testbed command exited with code 0 99s autopkgtest: DBG: testbed command ['bash', '-ec', 'for d in /boot /boot/efi /boot/grub /etc/init /etc/init.d /etc/systemd/system /lib/systemd/system; do [ ! -d $d ] || touch -r $d /tmp/autopkgtest.DF7m5L/${d//\\//_}.stamp; done'], kind short, sout raw, serr pipe, env [] 99s autopkgtest: DBG: testbed command exited with code 0 99s autopkgtest: DBG: testbed command ['sh', '-ec', '#!/bin/sh\n# Canonical/Ubuntu specific testbed setup\n\nset -x\n\nRELEASE=$(lsb_release --codename --short 2>/dev/null)\n\n# Make the installed package versions match what is available from the configured\n# repositories, even if a downgrade is required.\n#\n# We may end up with images with packages newer than those available from the\n# repositories when opening a new release (images are created using the\n# previous release dailies as a base, which may include 0-day SRUs, or\n# Launchpad may fail to copy packages, see openssl 3.0.8-1ubuntu2), or when\n# package versions are pulled from the archive.\n#\n# Note: \'release a=\' matches the Suite field in the repository Release file.\ncat >/etc/apt/preferences.d/force-downgrade-to-release.pref <= Focal).\n#\n# Note: autoremove/--autoremove always runs on the entire set of installed\n# packages. Together with --autopurge/purge each removal becomes a purge.\n#\n# Removing \'?obsolete\' packages may remove the running kernel. This is not\n# expected to be an issue.\nif /usr/lib/apt/apt-helper analyze-pattern \'?true\' >/dev/null 2>&1; then\n # DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y purge --autoremove \'?obsolete\'\n # Avoid removing the running kernel\n running_kernel_pattern="^linux-.*$(uname -r | sed \'s/\\./\\\\./g\').*"\n obsolete_pkgs="$(apt list \'?obsolete\' 2>/dev/null \\\n | tail -n+2 \\\n | cut -d\'/\' -f1 \\\n | grep -v "${running_kernel_pattern}" || true)"\n DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y purge --autoremove ${obsolete_pkgs}\nelse\n # We\'re on an older release (analyze-pattern is not available).\n # Still do an autopurge to get rid of packages that got orphaned\n # by downgrades.\n eatmydata apt-get -y autoremove --purge\nfi\n\n# compatibility with old Jenkins testbeds for trusty\nif grep -q trusty /etc/lsb-release; then apt-get update || (sleep 10; apt-get update); apt-get install -y build-essential; fi\n\n# these packages really break tests, purge them if we use standard cloud images\n# (on lcy01)\nfor p in unattended-upgrades lxd lxd-client snapd; do\n [ ! -d /usr/share/doc/$p ] || $(which eatmydata || true) apt-get purge --auto-remove -y $p\ndone\n\nif type iptables >/dev/null 2>&1; then\n cat < /etc/rc.local\n#!/bin/sh\n\n# work around broken PTMU; LP: #1572026, RT#90771\niptables -w -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu || true\n\n# These addresses are used at least by rust-reqwest and should not be reachable\n# See https://bugs.launchpad.net/ubuntu/+source/rust-reqwest/+bug/2080346\niptables -A OUTPUT -d 10.255.255.1/32 -p tcp -j DROP || true\niptables -A OUTPUT -d 10.255.255.2/32 -p tcp -j DROP || true\nEOF\n chmod 755 /etc/rc.local\n # shellcheck disable=SC1091\n . /etc/rc.local\nfi\n\n# work around broken tty on ppc64el instances (LP: #1607075)\nif [ "$(uname -m)" = ppc64le ] && [ "$(systemctl is-active keyboard-setup.service 2>/dev/null|| true)" = failed ]; then\n systemctl reset-failed keyboard-setup.service\n systemctl mask keyboard-setup.service\nfi\n\n# work around late urandom pool initialization (LP: #1622893)\nif [ -d /run/systemd/system ] && systemd-detect-virt --quiet --vm; then\n mkdir -p /etc/systemd/system/systemd-random-seed.service.d/\n cat < /etc/systemd/system/systemd-random-seed.service.d/fakeentropy.conf\n[Service]\nExecStart=/usr/bin/perl -E \'open \\$\\$f, "/bin/bash" or die; open \\$\\$rnd, ">/dev/random" or die; for (\\$\\$i = 0; \\$\\$i < 10; ++\\$\\$i) {read \\$\\$f, \\$\\$d, 64; ioctl \\$\\$rnd, 0x40085203, pack("ii", 64*8, 64) . \\$\\$d}\'\nEOF\nfi\n\n# set compressor to lz4 where supported, we care about compression speed\nif grep -q lz4 /etc/initramfs-tools/initramfs.conf; then\n echo COMPRESS=lz4 > /etc/initramfs-tools/conf.d/lz4\nfi'], kind install, sout raw, serr raw, env ['AUTOPKGTEST_IS_SETUP_COMMAND=1', 'AUTOPKGTEST_NORMAL_USER=ubuntu', 'ADT_NORMAL_USER=ubuntu'] 99s + lsb_release --codename --short 99s + RELEASE=plucky 99s + cat 99s + [ plucky != trusty ] 99s + DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y --allow-downgrades -o Dpkg::Options::=--force-confnew dist-upgrade 99s Reading package lists... 100s Building dependency tree... 100s Reading state information... 100s Calculating upgrade... 100s The following packages were automatically installed and are no longer required: 100s libnsl2 libpython3.12-minimal libpython3.12-stdlib libpython3.12t64 100s linux-headers-6.11.0-8 linux-headers-6.11.0-8-generic 100s linux-modules-6.11.0-8-generic linux-tools-6.11.0-8 100s linux-tools-6.11.0-8-generic 100s Use 'sudo apt autoremove' to remove them. 100s The following packages will be upgraded: 100s dash gcc-14-base libatomic1 libgcc-s1 libstdc++6 libtasn1-6 libxdmcp6 100s 7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 100s Need to get 1155 kB of archives. 100s After this operation, 16.4 kB of additional disk space will be used. 100s Get:1 http://ftpmaster.internal/ubuntu plucky/main s390x dash s390x 0.5.12-12ubuntu1 [100 kB] 100s Get:2 http://ftpmaster.internal/ubuntu plucky/main s390x libatomic1 s390x 14.2.0-17ubuntu1 [9430 B] 100s Get:3 http://ftpmaster.internal/ubuntu plucky/main s390x gcc-14-base s390x 14.2.0-17ubuntu1 [53.5 kB] 100s Get:4 http://ftpmaster.internal/ubuntu plucky/main s390x libstdc++6 s390x 14.2.0-17ubuntu1 [896 kB] 100s Get:5 http://ftpmaster.internal/ubuntu plucky/main s390x libgcc-s1 s390x 14.2.0-17ubuntu1 [35.9 kB] 100s Get:6 http://ftpmaster.internal/ubuntu plucky/main s390x libtasn1-6 s390x 4.20.0-2 [48.6 kB] 100s Get:7 http://ftpmaster.internal/ubuntu plucky/main s390x libxdmcp6 s390x 1:1.1.5-1 [11.0 kB] 101s Preconfiguring packages ... 101s Fetched 1155 kB in 1s (1901 kB/s) 101s (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 ... 80969 files and directories currently installed.) 101s Preparing to unpack .../dash_0.5.12-12ubuntu1_s390x.deb ... 101s Unpacking dash (0.5.12-12ubuntu1) over (0.5.12-9ubuntu1) ... 101s Setting up dash (0.5.12-12ubuntu1) ... 101s (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 ... 80969 files and directories currently installed.) 101s Preparing to unpack .../libatomic1_14.2.0-17ubuntu1_s390x.deb ... 101s Unpacking libatomic1:s390x (14.2.0-17ubuntu1) over (14.2.0-16ubuntu1) ... 101s Preparing to unpack .../gcc-14-base_14.2.0-17ubuntu1_s390x.deb ... 101s Unpacking gcc-14-base:s390x (14.2.0-17ubuntu1) over (14.2.0-16ubuntu1) ... 101s Setting up gcc-14-base:s390x (14.2.0-17ubuntu1) ... 101s (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 ... 80969 files and directories currently installed.) 101s Preparing to unpack .../libstdc++6_14.2.0-17ubuntu1_s390x.deb ... 101s Unpacking libstdc++6:s390x (14.2.0-17ubuntu1) over (14.2.0-16ubuntu1) ... 101s Setting up libstdc++6:s390x (14.2.0-17ubuntu1) ... 101s (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 ... 80969 files and directories currently installed.) 101s Preparing to unpack .../libgcc-s1_14.2.0-17ubuntu1_s390x.deb ... 101s Unpacking libgcc-s1:s390x (14.2.0-17ubuntu1) over (14.2.0-16ubuntu1) ... 101s Setting up libgcc-s1:s390x (14.2.0-17ubuntu1) ... 101s (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 ... 80969 files and directories currently installed.) 101s Preparing to unpack .../libtasn1-6_4.20.0-2_s390x.deb ... 101s Unpacking libtasn1-6:s390x (4.20.0-2) over (4.19.0-3build1) ... 101s Preparing to unpack .../libxdmcp6_1%3a1.1.5-1_s390x.deb ... 101s Unpacking libxdmcp6:s390x (1:1.1.5-1) over (1:1.1.3-0ubuntu6) ... 101s Setting up libxdmcp6:s390x (1:1.1.5-1) ... 101s Setting up libatomic1:s390x (14.2.0-17ubuntu1) ... 101s Setting up libtasn1-6:s390x (4.20.0-2) ... 101s Processing triggers for libc-bin (2.40-4ubuntu1) ... 101s Processing triggers for man-db (2.13.0-1) ... 101s Processing triggers for debianutils (5.21) ... 102s + rm /etc/apt/preferences.d/force-downgrade-to-release.pref 102s + /usr/lib/apt/apt-helper analyze-pattern ?true 102s + uname -r 102s + sed s/\./\\./g 102s + running_kernel_pattern=^linux-.*6\.12\.0-15-generic.* 102s + apt list ?obsolete 102s + + cut -d/ -f1 102s tail -n+2 102s + grep -v ^linux-.*6\.12\.0-15-generic.* 102s + true 102s + obsolete_pkgs= 102s + DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y purge --autoremove 102s Reading package lists... 102s Building dependency tree... 102s Reading state information... 102s The following packages will be REMOVED: 102s libnsl2* libpython3.12-minimal* libpython3.12-stdlib* libpython3.12t64* 102s linux-headers-6.11.0-8* linux-headers-6.11.0-8-generic* 102s linux-modules-6.11.0-8-generic* linux-tools-6.11.0-8* 102s linux-tools-6.11.0-8-generic* 102s 0 upgraded, 0 newly installed, 9 to remove and 6 not upgraded. 102s After this operation, 167 MB disk space will be freed. 102s (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 ... 80969 files and directories currently installed.) 102s Removing linux-tools-6.11.0-8-generic (6.11.0-8.8) ... 102s Removing linux-tools-6.11.0-8 (6.11.0-8.8) ... 102s Removing libpython3.12t64:s390x (3.12.9-1) ... 102s Removing libpython3.12-stdlib:s390x (3.12.9-1) ... 102s Removing libnsl2:s390x (1.3.0-3build3) ... 102s Removing libpython3.12-minimal:s390x (3.12.9-1) ... 102s Removing linux-headers-6.11.0-8-generic (6.11.0-8.8) ... 102s Removing linux-headers-6.11.0-8 (6.11.0-8.8) ... 103s Removing linux-modules-6.11.0-8-generic (6.11.0-8.8) ... 103s Processing triggers for libc-bin (2.40-4ubuntu1) ... 103s (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 ... 55869 files and directories currently installed.) 103s Purging configuration files for libpython3.12-minimal:s390x (3.12.9-1) ... 103s Purging configuration files for linux-modules-6.11.0-8-generic (6.11.0-8.8) ... 104s + grep -q trusty /etc/lsb-release 104s + [ ! -d /usr/share/doc/unattended-upgrades ] 104s + [ ! -d /usr/share/doc/lxd ] 104s + [ ! -d /usr/share/doc/lxd-client ] 104s + [ ! -d /usr/share/doc/snapd ] 104s + type iptables 104s + cat 104s + chmod 755 /etc/rc.local 104s + . /etc/rc.local 104s + iptables -w -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu 104s + iptables -A OUTPUT -d 10.255.255.1/32 -p tcp -j DROP 104s + iptables -A OUTPUT -d 10.255.255.2/32 -p tcp -j DROP 104s + uname -m 104s + [ s390x = ppc64le ] 104s + [ -d /run/systemd/system ] 104s + systemd-detect-virt --quiet --vm 104s + mkdir -p /etc/systemd/system/systemd-random-seed.service.d/ 104s + cat 104s + grep -q lz4 /etc/initramfs-tools/initramfs.conf 104s + echo COMPRESS=lz4 104s autopkgtest: DBG: testbed command exited with code 0 104s autopkgtest [23:59:56]: upgrading testbed (apt dist-upgrade and autopurge) 104s autopkgtest: DBG: testbed command ['/bin/sh', '-ec', '"$@" 3>&2 2>&1', 'run_apt_command', '/usr/bin/eatmydata', 'apt-get', '--quiet', '--assume-yes', '-o=APT::Status-Fd=3', '-o=APT::Install-Recommends=false', '-o=Dpkg::Options::=--force-confnew', '-o=Debug::pkgProblemResolver=true', 'dist-upgrade'], kind install, sout raw, serr pipe, env ['DEBIAN_FRONTEND=noninteractive', 'APT_LISTBUGS_FRONTEND=none', 'APT_LISTCHANGES_FRONTEND=none'] 104s Reading package lists... 104s Building dependency tree... 104s Reading state information... 104s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 104s Starting 2 pkgProblemResolver with broken count: 0 104s Done 104s Entering ResolveByKeep 104s 104s The following packages will be upgraded: 104s iproute2 libc-bin libc-dev-bin libc6 libc6-dev locales 105s 6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 105s Need to get 10.7 MB of archives. 105s After this operation, 305 kB of additional disk space will be used. 105s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x libc-dev-bin s390x 2.41-1ubuntu1 [24.3 kB] 105s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x libc6-dev s390x 2.41-1ubuntu1 [1679 kB] 105s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x locales all 2.41-1ubuntu1 [4246 kB] 105s Get:4 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x libc6 s390x 2.41-1ubuntu1 [2891 kB] 105s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x libc-bin s390x 2.41-1ubuntu1 [672 kB] 105s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x iproute2 s390x 6.13.0-1ubuntu1 [1174 kB] 106s Preconfiguring packages ... 106s Fetched 10.7 MB in 1s (10.8 MB/s) 106s (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 ... 55867 files and directories currently installed.) 106s Preparing to unpack .../libc-dev-bin_2.41-1ubuntu1_s390x.deb ... 106s Unpacking libc-dev-bin (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 106s Preparing to unpack .../libc6-dev_2.41-1ubuntu1_s390x.deb ... 106s Unpacking libc6-dev:s390x (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 106s Preparing to unpack .../locales_2.41-1ubuntu1_all.deb ... 106s Unpacking locales (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 106s Preparing to unpack .../libc6_2.41-1ubuntu1_s390x.deb ... 106s Checking for services that may need to be restarted... 106s Checking init scripts... 106s Checking for services that may need to be restarted... 106s Checking init scripts... 106s Stopping some services possibly affected by the upgrade (will be restarted later): 106s cron: stopping...done. 106s 106s Unpacking libc6:s390x (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 106s Setting up libc6:s390x (2.41-1ubuntu1) ... 106s Checking for services that may need to be restarted... 106s Checking init scripts... 106s Restarting services possibly affected by the upgrade: 106s cron: restarting...done. 106s 106s Services restarted successfully. 106s (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 ... 55868 files and directories currently installed.) 106s Preparing to unpack .../libc-bin_2.41-1ubuntu1_s390x.deb ... 106s Unpacking libc-bin (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 106s Setting up libc-bin (2.41-1ubuntu1) ... 106s (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 ... 55868 files and directories currently installed.) 106s Preparing to unpack .../iproute2_6.13.0-1ubuntu1_s390x.deb ... 107s Unpacking iproute2 (6.13.0-1ubuntu1) over (6.10.0-2ubuntu1) ... 107s Setting up iproute2 (6.13.0-1ubuntu1) ... 107s Setting up locales (2.41-1ubuntu1) ... 107s Installing new version of config file /etc/locale.alias ... 107s Generating locales (this might take a while)... 108s en_US.UTF-8... done 108s Generation complete. 108s Setting up libc-dev-bin (2.41-1ubuntu1) ... 108s Setting up libc6-dev:s390x (2.41-1ubuntu1) ... 108s Processing triggers for man-db (2.13.0-1) ... 110s Processing triggers for systemd (257.2-3ubuntu1) ... 110s autopkgtest: DBG: testbed command exited with code 0 110s autopkgtest: DBG: testbed command ['/bin/sh', '-ec', '"$@" 3>&2 2>&1', 'run_apt_command', '/usr/bin/eatmydata', 'apt-get', '--quiet', '--assume-yes', '-o=APT::Status-Fd=3', '-o=APT::Install-Recommends=false', '-o=Dpkg::Options::=--force-confnew', '-o=Debug::pkgProblemResolver=true', '--purge', 'autoremove'], kind install, sout raw, serr pipe, env ['DEBIAN_FRONTEND=noninteractive', 'APT_LISTBUGS_FRONTEND=none', 'APT_LISTCHANGES_FRONTEND=none'] 110s autopkgtest: DBG: testbed command exited with code 0 110s autopkgtest: DBG: testbed command ['bash', '-ec', '[ ! -e /run/autopkgtest_no_reboot.stamp ] || exit 0;for d in /boot /boot/efi /boot/grub /etc/init /etc/init.d /etc/systemd/system /lib/systemd/system; do s=/tmp/autopkgtest.DF7m5L/${d//\\//_}.stamp; [ ! -d $d ] || [ `stat -c %Y $d` = `stat -c %Y $s` ]; done'], kind short, sout raw, serr raw, env [] 110s Reading package lists... 110s Building dependency tree... 110s Reading state information... 110s Starting pkgProblemResolver with broken count: 0 110s Starting 2 pkgProblemResolver with broken count: 0 110s Done 110s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 110s autopkgtest: DBG: testbed command exited with code 1 110s autopkgtest [00:00:02]: rebooting testbed after setup commands that affected boot 110s autopkgtest: DBG: sending command to testbed: reboot 127s autopkgtest: DBG: got reply from testbed: ok 127s autopkgtest: DBG: testbed supports reboot, creating /tmp/autopkgtest-reboot 127s autopkgtest: DBG: testbed command ['mkdir', '-p', '/tmp/autopkgtest.DF7m5L'], kind short, sout raw, serr pipe, env [] 127s autopkgtest: DBG: testbed command exited with code 0 127s autopkgtest: DBG: sending command to testbed: copydown /home/ubuntu/autopkgtest/lib/in-testbed/reboot.sh /tmp/autopkgtest.DF7m5L/autopkgtest-reboot 128s autopkgtest: DBG: got reply from testbed: ok 128s autopkgtest: DBG: testbed command ['chmod', '-R', '0755', '--', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot'], kind short, sout raw, serr pipe, env [] 128s autopkgtest: DBG: testbed command exited with code 0 128s autopkgtest: DBG: testbed command ['ln', '-fns', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot', '/tmp/autopkgtest-reboot'], kind short, sout raw, serr pipe, env [] 128s autopkgtest: DBG: testbed command exited with code 0 128s autopkgtest: DBG: testbed command ['ln', '-fns', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot', '/sbin/autopkgtest-reboot'], kind short, sout raw, serr pipe, env [] 128s autopkgtest: DBG: testbed command exited with code 0 128s autopkgtest: DBG: testbed command ['mkdir', '-p', '/tmp/autopkgtest.DF7m5L'], kind short, sout raw, serr pipe, env [] 128s autopkgtest: DBG: testbed command exited with code 0 128s autopkgtest: DBG: sending command to testbed: copydown /home/ubuntu/autopkgtest/lib/in-testbed/reboot-prepare.sh /tmp/autopkgtest.DF7m5L/autopkgtest-reboot-prepare 129s autopkgtest: DBG: got reply from testbed: ok 129s autopkgtest: DBG: testbed command ['chmod', '-R', '0755', '--', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot-prepare'], kind short, sout raw, serr pipe, env [] 129s autopkgtest: DBG: testbed command exited with code 0 129s autopkgtest: DBG: testbed command ['ln', '-fns', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot-prepare', '/tmp/autopkgtest-reboot-prepare'], kind short, sout raw, serr pipe, env [] 129s autopkgtest: DBG: testbed command exited with code 0 129s autopkgtest: DBG: testbed command ['uname', '-srv'], kind short, sout pipe, serr pipe, env [] 129s autopkgtest: DBG: testbed command exited with code 0 129s autopkgtest [00:00:21]: testbed running kernel: Linux 6.12.0-15-generic #15-Ubuntu SMP Tue Feb 4 15:05:57 UTC 2025 129s autopkgtest: DBG: testbed command ['sh', '-c', 'nproc; cat /proc/cpuinfo 2>/dev/null || true'], kind short, sout pipe, serr pipe, env [] 129s autopkgtest: DBG: testbed command exited with code 0 129s autopkgtest: DBG: testbed command ['sh', '-ec', "dpkg-query --show -f '${Package}\\t${Version}\\n' > /tmp/autopkgtest.DF7m5L/testbed-packages"], kind short, sout raw, serr pipe, env [] 129s autopkgtest: DBG: testbed command exited with code 0 129s autopkgtest: DBG: sending command to testbed: copyup /tmp/autopkgtest.DF7m5L/testbed-packages /tmp/autopkgtest-work.5ogut_s7/out/testbed-packages 130s autopkgtest: DBG: got reply from testbed: ok 130s autopkgtest: DBG: testbed supports reboot, creating /tmp/autopkgtest-reboot 130s autopkgtest: DBG: testbed command ['mkdir', '-p', '/tmp/autopkgtest.DF7m5L'], kind short, sout raw, serr pipe, env [] 130s autopkgtest: DBG: testbed command exited with code 0 130s autopkgtest: DBG: sending command to testbed: copydown /home/ubuntu/autopkgtest/lib/in-testbed/reboot.sh /tmp/autopkgtest.DF7m5L/autopkgtest-reboot 130s autopkgtest: DBG: got reply from testbed: ok 130s autopkgtest: DBG: testbed command ['chmod', '-R', '0755', '--', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot'], kind short, sout raw, serr pipe, env [] 130s autopkgtest: DBG: testbed command exited with code 0 130s autopkgtest: DBG: testbed command ['ln', '-fns', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot', '/tmp/autopkgtest-reboot'], kind short, sout raw, serr pipe, env [] 130s autopkgtest: DBG: testbed command exited with code 0 130s autopkgtest: DBG: testbed command ['ln', '-fns', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot', '/sbin/autopkgtest-reboot'], kind short, sout raw, serr pipe, env [] 130s autopkgtest: DBG: testbed command exited with code 0 130s autopkgtest: DBG: testbed command ['mkdir', '-p', '/tmp/autopkgtest.DF7m5L'], kind short, sout raw, serr pipe, env [] 131s autopkgtest: DBG: testbed command exited with code 0 131s autopkgtest: DBG: sending command to testbed: copydown /home/ubuntu/autopkgtest/lib/in-testbed/reboot-prepare.sh /tmp/autopkgtest.DF7m5L/autopkgtest-reboot-prepare 131s autopkgtest: DBG: got reply from testbed: ok 131s autopkgtest: DBG: testbed command ['chmod', '-R', '0755', '--', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot-prepare'], kind short, sout raw, serr pipe, env [] 131s autopkgtest: DBG: testbed command exited with code 0 131s autopkgtest: DBG: testbed command ['ln', '-fns', '/tmp/autopkgtest.DF7m5L/autopkgtest-reboot-prepare', '/tmp/autopkgtest-reboot-prepare'], kind short, sout raw, serr pipe, env [] 131s autopkgtest: DBG: testbed command exited with code 0 131s autopkgtest: DBG: testbed command ['uname', '-srv'], kind short, sout pipe, serr pipe, env [] 131s autopkgtest: DBG: testbed command exited with code 0 131s autopkgtest: DBG: Binaries: initialising 131s autopkgtest [00:00:23]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 131s autopkgtest: DBG: blame += libfprint 131s autopkgtest: DBG: testbed reset: modified=False, deps_installed=[], deps_new=[] 131s autopkgtest: DBG: testbed command ['apt-cache', 'showsrc', '--only-source', 'libfprint'], kind short, sout pipe, serr pipe, env [] 132s autopkgtest: DBG: testbed command exited with code 0 132s autopkgtest: DBG: testbed command ['apt-cache', 'policy', '^libfprint-2-doc$'], kind short, sout pipe, serr raw, env [] 132s autopkgtest: DBG: testbed command exited with code 0 132s autopkgtest: DBG: testbed command ['apt-cache', 'show', 'libfprint-2-doc=1:1.94.8+tod1-0ubuntu1'], kind short, sout pipe, serr raw, env [] 132s autopkgtest: DBG: testbed command exited with code 0 132s autopkgtest: DBG: testbed command ['apt-cache', 'policy', '^libfprint-2-dev$'], kind short, sout pipe, serr raw, env [] 132s autopkgtest: DBG: testbed command exited with code 0 132s autopkgtest: DBG: testbed command ['apt-cache', 'show', 'libfprint-2-dev=1:1.94.8+tod1-0ubuntu1'], kind short, sout pipe, serr raw, env [] 133s autopkgtest: DBG: testbed command exited with code 0 133s autopkgtest: DBG: testbed command ['apt-cache', 'policy', '^libfprint-2-tests$'], kind short, sout pipe, serr raw, env [] 133s autopkgtest: DBG: testbed command exited with code 0 133s autopkgtest: DBG: testbed command ['apt-cache', 'show', 'libfprint-2-tests=1:1.94.8+tod1-0ubuntu1'], kind short, sout pipe, serr raw, env [] 133s autopkgtest: DBG: testbed command exited with code 0 133s autopkgtest: DBG: testbed command ['apt-cache', 'policy', '^gir1\\.2-fprint-2\\.0$'], kind short, sout pipe, serr raw, env [] 133s autopkgtest: DBG: testbed command exited with code 0 133s autopkgtest: DBG: testbed command ['apt-cache', 'show', 'gir1.2-fprint-2.0=1:1.94.8+tod1-0ubuntu1'], kind short, sout pipe, serr raw, env [] 133s autopkgtest: DBG: testbed command exited with code 0 133s autopkgtest: DBG: testbed command ['apt-cache', 'policy', '^libfprint-2-tod1$'], kind short, sout pipe, serr raw, env [] 134s autopkgtest: DBG: testbed command exited with code 0 134s autopkgtest: DBG: testbed command ['apt-cache', 'show', 'libfprint-2-tod1=1:1.94.8+tod1-0ubuntu1'], kind short, sout pipe, serr raw, env [] 134s autopkgtest: DBG: testbed command exited with code 0 134s autopkgtest: DBG: testbed command ['apt-cache', 'policy', '^libfprint-2-tod-dev$'], kind short, sout pipe, serr raw, env [] 134s autopkgtest: DBG: testbed command exited with code 0 134s autopkgtest: DBG: testbed command ['apt-cache', 'show', 'libfprint-2-tod-dev=1:1.94.8+tod1-0ubuntu1'], kind short, sout pipe, serr raw, env [] 134s autopkgtest: DBG: testbed command exited with code 0 134s autopkgtest: DBG: testbed command ['apt-cache', 'policy', '^libfprint-2-2$'], kind short, sout pipe, serr raw, env [] 134s autopkgtest: DBG: testbed command exited with code 0 134s autopkgtest: DBG: testbed command ['apt-cache', 'show', 'libfprint-2-2=1:1.94.8+tod1-0ubuntu1'], kind short, sout pipe, serr raw, env [] 135s autopkgtest: DBG: testbed command exited with code 0 135s autopkgtest: DBG: install_deps: deps_new=[] 135s autopkgtest: DBG: testbed command ['sh', '-ec', 'command -v dpkg-source'], kind short, sout pipe, serr pipe, env [] 135s autopkgtest: DBG: testbed command exited with code 0 135s autopkgtest: DBG: testbed command ['sh', '-ec', 'su --shell=/bin/sh ubuntu -c \'set -e; exec 3>&1 >&2; set -x; cd /; builddir=$(mktemp -d /tmp/autopkgtest.DF7m5L/build.XXX); cd $builddir; OUT=$(apt-get source -d -q --only-source libfprint=1:1.94.8+tod1-0ubuntu1 2>&1) || RC=$?;if [ -n "$RC" ]; then if echo "$OUT" | grep -q "Unable to find a source package"; then exit 1; else exit $RC; fi;fi;echo "$OUT" | grep ^Get: || true;dpkg-source -x libfprint_*.dsc src >/dev/null; chmod -R a+rX .; cd [a-z0-9]*/.; pwd >&3; sed -n "1 {s/).*//; s/ (/\\n/; p}" debian/changelog >&3\''], kind build, sout pipe, serr raw, env ['ADT_TEST_TRIGGERS=glibc/2.41-1ubuntu1 iproute2/6.13.0-1ubuntu1 php-twig/3.19.0-1 postgresql-17/17.3-2 postgresql-common/273 roundcube/1.6.10+dfsg-1'] 135s + cd / 135s + mktemp -d /tmp/autopkgtest.DF7m5L/build.XXX 135s + builddir=/tmp/autopkgtest.DF7m5L/build.Vr9 135s + cd /tmp/autopkgtest.DF7m5L/build.Vr9 135s + apt-get source -d -q --only-source libfprint=1:1.94.8+tod1-0ubuntu1 136s + OUT=Reading package lists... 136s NOTICE: 'libfprint' packaging is maintained in the 'Git' version control system at: 136s https://salsa.debian.org/ubuntu-dev-team/libfprint.git -b ubuntu 136s Please use: 136s git clone https://salsa.debian.org/ubuntu-dev-team/libfprint.git -b ubuntu 136s to retrieve the latest (possibly unreleased) updates to the package. 136s Need to get 9298 kB of source archives. 136s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (dsc) [2928 B] 136s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (tar) [9278 kB] 136s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (diff) [17.5 kB] 136s Fetched 9298 kB in 1s (10.3 MB/s) 136s Download complete and in download only mode 136s + [ -n ] 136s + grep ^Get: 136s + echo Reading package lists... 136s NOTICE: 'libfprint' packaging is maintained in the 'Git' version control system at: 136s https://salsa.debian.org/ubuntu-dev-team/libfprint.git -b ubuntu 136s Please use: 136s git clone https://salsa.debian.org/ubuntu-dev-team/libfprint.git -b ubuntu 136s to retrieve the latest (possibly unreleased) updates to the package. 136s Need to get 9298 kB of source archives. 136s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (dsc) [2928 B] 136s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (tar) [9278 kB] 136s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (diff) [17.5 kB] 136s Fetched 9298 kB in 1s (10.3 MB/s) 136s Download complete and in download only mode 136s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (dsc) [2928 B] 136s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (tar) [9278 kB] 136s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (diff) [17.5 kB] 136s + dpkg-source -x libfprint_1.94.8+tod1-0ubuntu1.dsc src 136s gpgv: Signature made Tue Sep 3 05:15:30 2024 UTC 136s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 136s gpgv: Can't check signature: No public key 136s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.8+tod1-0ubuntu1.dsc: no acceptable signature found 137s + chmod -R a+rX . 137s + cd src/. 137s + pwd 137s + sed -n 1 {s/).*//; s/ (/\n/; p} debian/changelog 137s autopkgtest: DBG: testbed command exited with code 0 137s autopkgtest [00:00:29]: testing package libfprint version 1:1.94.8+tod1-0ubuntu1 137s autopkgtest: DBG: sending command to testbed: copyup /tmp/autopkgtest.DF7m5L/build.Vr9/src/debian/ /tmp/autopkgtest-work.5ogut_s7/out/pkg/debian/ 137s autopkgtest: DBG: got reply from testbed: ok 138s autopkgtest: DBG: processing dependency gnome-desktop-testing 138s autopkgtest: DBG: processing dependency libfprint-2-tests 138s autopkgtest: DBG: marked alternatives ['libfprint-2-tests'] as a synthesised dependency 138s autopkgtest: DBG: Test defined: name installed-tests path None command "gnome-desktop-testing-runner libfprint-2" restrictions ['allow-stderr'] features ['test-name=installed-tests'] depends ['gnome-desktop-testing', 'libfprint-2-tests'] 138s autopkgtest [00:00:30]: build not needed 138s autopkgtest: DBG: sending command to testbed: copyup /tmp/autopkgtest.DF7m5L/build.Vr9/src/ /tmp/autopkgtest-work.5ogut_s7/out/tests-tree/ 139s autopkgtest: DBG: got reply from testbed: ok 139s autopkgtest: DBG: processing dependency gnome-desktop-testing 139s autopkgtest: DBG: processing dependency libfprint-2-tests 139s autopkgtest: DBG: marked alternatives ['libfprint-2-tests'] as a synthesised dependency 139s autopkgtest: DBG: Test defined: name installed-tests path None command "gnome-desktop-testing-runner libfprint-2" restrictions ['allow-stderr'] features ['test-name=installed-tests'] depends ['gnome-desktop-testing', 'libfprint-2-tests'] 139s autopkgtest [00:00:31]: test installed-tests: preparing testbed 139s autopkgtest: DBG: testbed reset: modified=False, deps_installed=[], deps_new=['gnome-desktop-testing', 'libfprint-2-tests'] 139s autopkgtest: DBG: Binaries: no registered binaries, not publishing anything 139s autopkgtest: DBG: install_deps: deps_new=['gnome-desktop-testing', 'libfprint-2-tests'] 139s autopkgtest: DBG: install-deps: satisfying gnome-desktop-testing, libfprint-2-tests 139s autopkgtest: DBG: can use apt-get on testbed: True 139s autopkgtest: DBG: testbed command ['/bin/sh', '-ec', '"$@" 3>&2 2>&1', 'run_apt_command', '/usr/bin/eatmydata', 'apt-get', '--quiet', '--assume-yes', '-o=APT::Status-Fd=3', '-o=APT::Install-Recommends=false', '-o=Dpkg::Options::=--force-confnew', '-o=Debug::pkgProblemResolver=true', 'satisfy', 'gnome-desktop-testing, libfprint-2-tests'], kind install, sout raw, serr pipe, env ['DEBIAN_FRONTEND=noninteractive', 'APT_LISTBUGS_FRONTEND=none', 'APT_LISTCHANGES_FRONTEND=none'] 140s Reading package lists... 140s Building dependency tree... 140s Reading state information... 140s Starting pkgProblemResolver with broken count: 0 140s Starting 2 pkgProblemResolver with broken count: 0 140s Done 140s The following NEW packages will be installed: 140s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 140s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 140s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 libfreetype6 140s libgusb2 libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 140s python3-cairo umockdev 140s 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. 140s Need to get 5351 kB of archives. 140s After this operation, 15.5 MB of additional disk space will be used. 140s Get:1 http://ftpmaster.internal/ubuntu plucky/main s390x fonts-dejavu-mono all 2.37-8 [502 kB] 141s Get:2 http://ftpmaster.internal/ubuntu plucky/main s390x fonts-dejavu-core all 2.37-8 [835 kB] 141s Get:3 http://ftpmaster.internal/ubuntu plucky/main s390x fontconfig-config s390x 2.15.0-1.1ubuntu2 [37.4 kB] 141s Get:4 http://ftpmaster.internal/ubuntu plucky/main s390x gir1.2-json-1.0 s390x 1.10.6+ds-1 [9920 B] 141s Get:5 http://ftpmaster.internal/ubuntu plucky/main s390x libgusb2 s390x 0.4.9-1 [38.9 kB] 141s Get:6 http://ftpmaster.internal/ubuntu plucky/main s390x gir1.2-gusb-1.0 s390x 0.4.9-1 [7370 B] 141s Get:7 http://ftpmaster.internal/ubuntu plucky/main s390x libpixman-1-0 s390x 0.44.0-3 [201 kB] 141s Get:8 http://ftpmaster.internal/ubuntu plucky/main s390x libfprint-2-tod1 s390x 1:1.94.8+tod1-0ubuntu1 [65.4 kB] 141s Get:9 http://ftpmaster.internal/ubuntu plucky/main s390x libfprint-2-2 s390x 1:1.94.8+tod1-0ubuntu1 [203 kB] 141s Get:10 http://ftpmaster.internal/ubuntu plucky/main s390x gir1.2-fprint-2.0 s390x 1:1.94.8+tod1-0ubuntu1 [7166 B] 141s Get:11 http://ftpmaster.internal/ubuntu plucky/universe s390x gnome-desktop-testing s390x 2021.1-4 [16.6 kB] 141s Get:12 http://ftpmaster.internal/ubuntu plucky/main s390x libfreetype6 s390x 2.13.3+dfsg-1 [431 kB] 141s Get:13 http://ftpmaster.internal/ubuntu plucky/main s390x libfontconfig1 s390x 2.15.0-1.1ubuntu2 [150 kB] 141s Get:14 http://ftpmaster.internal/ubuntu plucky/main s390x libxcb-render0 s390x 1.17.0-2 [17.0 kB] 141s Get:15 http://ftpmaster.internal/ubuntu plucky/main s390x libxcb-shm0 s390x 1.17.0-2 [5862 B] 141s Get:16 http://ftpmaster.internal/ubuntu plucky/main s390x libxrender1 s390x 1:0.9.10-1.1build1 [20.4 kB] 141s Get:17 http://ftpmaster.internal/ubuntu plucky/main s390x libcairo2 s390x 1.18.2-2 [580 kB] 141s Get:18 http://ftpmaster.internal/ubuntu plucky/main s390x python3-cairo s390x 1.26.1-2build1 [138 kB] 141s Get:19 http://ftpmaster.internal/ubuntu plucky/universe s390x libumockdev0 s390x 0.19.1-3 [77.1 kB] 141s Get:20 http://ftpmaster.internal/ubuntu plucky/universe s390x umockdev s390x 0.19.1-3 [75.1 kB] 141s Get:21 http://ftpmaster.internal/ubuntu plucky/universe s390x libfprint-2-tests s390x 1:1.94.8+tod1-0ubuntu1 [1933 kB] 141s Fetched 5351 kB in 1s (6021 kB/s) 141s Selecting previously unselected package fonts-dejavu-mono. 141s (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 ... 55869 files and directories currently installed.) 141s Preparing to unpack .../00-fonts-dejavu-mono_2.37-8_all.deb ... 141s Unpacking fonts-dejavu-mono (2.37-8) ... 141s Selecting previously unselected package fonts-dejavu-core. 141s Preparing to unpack .../01-fonts-dejavu-core_2.37-8_all.deb ... 141s Unpacking fonts-dejavu-core (2.37-8) ... 141s Selecting previously unselected package fontconfig-config. 141s Preparing to unpack .../02-fontconfig-config_2.15.0-1.1ubuntu2_s390x.deb ... 141s Unpacking fontconfig-config (2.15.0-1.1ubuntu2) ... 141s Selecting previously unselected package gir1.2-json-1.0:s390x. 141s Preparing to unpack .../03-gir1.2-json-1.0_1.10.6+ds-1_s390x.deb ... 141s Unpacking gir1.2-json-1.0:s390x (1.10.6+ds-1) ... 141s Selecting previously unselected package libgusb2:s390x. 141s Preparing to unpack .../04-libgusb2_0.4.9-1_s390x.deb ... 141s Unpacking libgusb2:s390x (0.4.9-1) ... 141s Selecting previously unselected package gir1.2-gusb-1.0:s390x. 141s Preparing to unpack .../05-gir1.2-gusb-1.0_0.4.9-1_s390x.deb ... 141s Unpacking gir1.2-gusb-1.0:s390x (0.4.9-1) ... 141s Selecting previously unselected package libpixman-1-0:s390x. 141s Preparing to unpack .../06-libpixman-1-0_0.44.0-3_s390x.deb ... 141s Unpacking libpixman-1-0:s390x (0.44.0-3) ... 142s Selecting previously unselected package libfprint-2-tod1:s390x. 142s Preparing to unpack .../07-libfprint-2-tod1_1%3a1.94.8+tod1-0ubuntu1_s390x.deb ... 142s Unpacking libfprint-2-tod1:s390x (1:1.94.8+tod1-0ubuntu1) ... 142s Selecting previously unselected package libfprint-2-2. 142s Preparing to unpack .../08-libfprint-2-2_1%3a1.94.8+tod1-0ubuntu1_s390x.deb ... 142s Unpacking libfprint-2-2 (1:1.94.8+tod1-0ubuntu1) ... 142s Selecting previously unselected package gir1.2-fprint-2.0:s390x. 142s Preparing to unpack .../09-gir1.2-fprint-2.0_1%3a1.94.8+tod1-0ubuntu1_s390x.deb ... 142s Unpacking gir1.2-fprint-2.0:s390x (1:1.94.8+tod1-0ubuntu1) ... 142s Selecting previously unselected package gnome-desktop-testing. 142s Preparing to unpack .../10-gnome-desktop-testing_2021.1-4_s390x.deb ... 142s Unpacking gnome-desktop-testing (2021.1-4) ... 142s Selecting previously unselected package libfreetype6:s390x. 142s Preparing to unpack .../11-libfreetype6_2.13.3+dfsg-1_s390x.deb ... 142s Unpacking libfreetype6:s390x (2.13.3+dfsg-1) ... 142s Selecting previously unselected package libfontconfig1:s390x. 142s Preparing to unpack .../12-libfontconfig1_2.15.0-1.1ubuntu2_s390x.deb ... 142s Unpacking libfontconfig1:s390x (2.15.0-1.1ubuntu2) ... 142s Selecting previously unselected package libxcb-render0:s390x. 142s Preparing to unpack .../13-libxcb-render0_1.17.0-2_s390x.deb ... 142s Unpacking libxcb-render0:s390x (1.17.0-2) ... 142s Selecting previously unselected package libxcb-shm0:s390x. 142s Preparing to unpack .../14-libxcb-shm0_1.17.0-2_s390x.deb ... 142s Unpacking libxcb-shm0:s390x (1.17.0-2) ... 142s Selecting previously unselected package libxrender1:s390x. 142s Preparing to unpack .../15-libxrender1_1%3a0.9.10-1.1build1_s390x.deb ... 142s Unpacking libxrender1:s390x (1:0.9.10-1.1build1) ... 142s Selecting previously unselected package libcairo2:s390x. 142s Preparing to unpack .../16-libcairo2_1.18.2-2_s390x.deb ... 142s Unpacking libcairo2:s390x (1.18.2-2) ... 142s Selecting previously unselected package python3-cairo. 142s Preparing to unpack .../17-python3-cairo_1.26.1-2build1_s390x.deb ... 142s Unpacking python3-cairo (1.26.1-2build1) ... 142s Selecting previously unselected package libumockdev0:s390x. 142s Preparing to unpack .../18-libumockdev0_0.19.1-3_s390x.deb ... 142s Unpacking libumockdev0:s390x (0.19.1-3) ... 142s Selecting previously unselected package umockdev. 142s Preparing to unpack .../19-umockdev_0.19.1-3_s390x.deb ... 142s Unpacking umockdev (0.19.1-3) ... 142s Selecting previously unselected package libfprint-2-tests. 142s Preparing to unpack .../20-libfprint-2-tests_1%3a1.94.8+tod1-0ubuntu1_s390x.deb ... 142s Unpacking libfprint-2-tests (1:1.94.8+tod1-0ubuntu1) ... 142s Setting up gnome-desktop-testing (2021.1-4) ... 142s Setting up libpixman-1-0:s390x (0.44.0-3) ... 142s Setting up libxrender1:s390x (1:0.9.10-1.1build1) ... 142s Setting up libxcb-render0:s390x (1.17.0-2) ... 142s Setting up libgusb2:s390x (0.4.9-1) ... 142s Setting up libfprint-2-tod1:s390x (1:1.94.8+tod1-0ubuntu1) ... 142s Setting up libxcb-shm0:s390x (1.17.0-2) ... 142s Setting up libfreetype6:s390x (2.13.3+dfsg-1) ... 142s Setting up fonts-dejavu-mono (2.37-8) ... 142s Setting up fonts-dejavu-core (2.37-8) ... 142s Setting up libumockdev0:s390x (0.19.1-3) ... 142s Setting up gir1.2-json-1.0:s390x (1.10.6+ds-1) ... 142s Setting up libfprint-2-2 (1:1.94.8+tod1-0ubuntu1) ... 144s Setting up umockdev (0.19.1-3) ... 144s Setting up fontconfig-config (2.15.0-1.1ubuntu2) ... 144s Setting up gir1.2-gusb-1.0:s390x (0.4.9-1) ... 144s Setting up libfontconfig1:s390x (2.15.0-1.1ubuntu2) ... 144s Setting up gir1.2-fprint-2.0:s390x (1:1.94.8+tod1-0ubuntu1) ... 144s Setting up libcairo2:s390x (1.18.2-2) ... 144s Setting up python3-cairo (1.26.1-2build1) ... 144s Setting up libfprint-2-tests (1:1.94.8+tod1-0ubuntu1) ... 144s Processing triggers for man-db (2.13.0-1) ... 144s Processing triggers for udev (257.2-3ubuntu1) ... 145s Processing triggers for libc-bin (2.41-1ubuntu1) ... 145s autopkgtest: DBG: testbed command exited with code 0 145s autopkgtest: DBG: testbed command ['dpkg-query', '--show', '-f', '${Status}', 'libfprint-2-tests'], kind short, sout pipe, serr pipe, env [] 145s autopkgtest: DBG: testbed command exited with code 0 145s autopkgtest: DBG: testbed command ['sh', '-ec', "dpkg-query --show -f '${Package}\\t${Version}\\n' > /tmp/autopkgtest.DF7m5L/installed-tests-packages.all"], kind short, sout raw, serr pipe, env [] 145s autopkgtest: DBG: testbed command exited with code 0 145s autopkgtest: DBG: sending command to testbed: copyup /tmp/autopkgtest.DF7m5L/installed-tests-packages.all /tmp/autopkgtest-work.5ogut_s7/out/installed-tests-packages.all 145s autopkgtest: DBG: got reply from testbed: ok 145s autopkgtest: DBG: testbed command ['test', '-e', '/tmp/autopkgtest.DF7m5L/build.Vr9/src'], kind short, sout raw, serr raw, env [] 145s autopkgtest: DBG: testbed command exited with code 0 145s autopkgtest: DBG: copydown: tb path /tmp/autopkgtest.DF7m5L/build.Vr9/src already exists 145s autopkgtest [00:00:37]: test installed-tests: gnome-desktop-testing-runner libfprint-2 145s autopkgtest [00:00:37]: test installed-tests: [----------------------- 145s autopkgtest: DBG: testbed command ['su', '-s', '/bin/bash', 'ubuntu', '-c', "set -e; exec /tmp/autopkgtest.DF7m5L/wrapper.sh --debug --artifacts=/tmp/autopkgtest.DF7m5L/installed-tests-artifacts --chdir=/tmp/autopkgtest.DF7m5L/build.Vr9/src --env=AUTOPKGTEST_TESTBED_ARCH=s390x --env=AUTOPKGTEST_TEST_ARCH=s390x --env=DEB_BUILD_OPTIONS=parallel=2 --env=DEBIAN_FRONTEND=noninteractive --env=LANG=C.UTF-8 --unset-env=LANGUAGE --unset-env=LC_ADDRESS --unset-env=LC_ALL --unset-env=LC_COLLATE --unset-env=LC_CTYPE --unset-env=LC_IDENTIFICATION --unset-env=LC_MEASUREMENT --unset-env=LC_MESSAGES --unset-env=LC_MONETARY --unset-env=LC_NAME --unset-env=LC_NUMERIC --unset-env=LC_PAPER --unset-env=LC_TELEPHONE --unset-env=LC_TIME --script-pid-file=/tmp/autopkgtest_script_pid --source-profile --stderr=/tmp/autopkgtest.DF7m5L/installed-tests-stderr --stdout=/tmp/autopkgtest.DF7m5L/installed-tests-stdout --tmp=/tmp/autopkgtest.DF7m5L/autopkgtest_tmp '--env=ADT_TEST_TRIGGERS=glibc/2.41-1ubuntu1 iproute2/6.13.0-1ubuntu1 php-twig/3.19.0-1 postgresql-17/17.3-2 postgresql-common/273 roundcube/1.6.10+dfsg-1' -- bash -ec 'gnome-desktop-testing-runner libfprint-2'"], kind test, sout raw, serr raw, env [] 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: creating AUTOPKGTEST_ARTIFACTS: /tmp/autopkgtest.DF7m5L/installed-tests-artifacts 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: changing to directory: /tmp/autopkgtest.DF7m5L/build.Vr9/src 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: setting environment: AUTOPKGTEST_TESTBED_ARCH=s390x 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: setting environment: AUTOPKGTEST_TEST_ARCH=s390x 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: setting environment: DEB_BUILD_OPTIONS=parallel=2 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: setting environment: DEBIAN_FRONTEND=noninteractive 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: setting environment: LANG=C.UTF-8 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LANGUAGE 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_ADDRESS 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_ALL 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_COLLATE 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_CTYPE 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_IDENTIFICATION 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_MEASUREMENT 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_MESSAGES 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_MONETARY 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_NAME 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_NUMERIC 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_PAPER 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_TELEPHONE 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: unsetting environment: LC_TIME 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: will create pid file: /tmp/autopkgtest_script_pid 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: pretending to be a login shell 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: will write standard error to /tmp/autopkgtest.DF7m5L/installed-tests-stderr 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: will write stdout to /tmp/autopkgtest.DF7m5L/installed-tests-stdout 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: creating AUTOPKGTEST_TMP: /tmp/autopkgtest.DF7m5L/autopkgtest_tmp 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: setting environment: ADT_TEST_TRIGGERS=glibc/2.41-1ubuntu1 iproute2/6.13.0-1ubuntu1 php-twig/3.19.0-1 postgresql-17/17.3-2 postgresql-common/273 roundcube/1.6.10+dfsg-1 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: command to run: bash -ec gnome-desktop-testing-runner libfprint-2 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: copying /tmp/tmp.yYELPovz31/out to stdout and file: /tmp/autopkgtest.DF7m5L/installed-tests-stdout 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: copying /tmp/tmp.yYELPovz31/err to standard error and file: /tmp/autopkgtest.DF7m5L/installed-tests-stdout 146s /tmp/autopkgtest.DF7m5L/wrapper.sh: writing script pid 2263 to /tmp/autopkgtest_script_pid 146s Running test: libfprint-2/virtual-image.test 146s (process:2284): libfprint-context-DEBUG: 00:02:03.887: Initializing FpContext (libfprint version 1.94.8+tod1) 146s (process:2284): libfprint-tod-DEBUG: 00:02:03.887: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 146s (process:2284): libfprint-context-DEBUG: 00:02:03.888: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-hr4krb3e/virtual-image.socket 146s (process:2284): libfprint-context-DEBUG: 00:02:03.888: created 146s (process:2284): libfprint-device-DEBUG: 00:02:03.888: Device reported probe completion 146s (process:2284): libfprint-device-DEBUG: 00:02:03.888: Completing action FPI_DEVICE_ACTION_PROBE in idle! 146s (process:2284): libfprint-device-DEBUG: 00:02:03.888: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:2284): libfprint-virtual_image-DEBUG: 00:02:03.893: 31112833: ../libfprint/drivers/virtual-image.c:216 146s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:02:03.893: 31112869: ../libfprint/drivers/virtual-device-listener.c:153 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.993: Image device open completed 146s (process:2284): libfprint-device-DEBUG: 00:02:03.993: Device reported open completion 146s (process:2284): libfprint-device-DEBUG: 00:02:03.993: Completing action FPI_DEVICE_ACTION_OPEN in idle! 146s (process:2284): libfprint-device-DEBUG: 00:02:03.993: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (process:2284): libfprint-device-DEBUG: 00:02:03.994: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Activating image device 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Image device activation completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 146s (process:2284): libfprint-device-DEBUG: 00:02:03.994: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:02:03.994: Got a new connection! 146s (process:2284): libfprint-device-DEBUG: 00:02:03.994: Idle cancelling on ongoing operation! 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Deactivating image device 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Image device deactivation completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:03.994: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 146s (process:2284): libfprint-device-DEBUG: 00:02:03.994: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 146s (process:2284): libfprint-device-DEBUG: 00:02:03.994: Device reported capture completion 146s (process:2284): libfprint-device-DEBUG: 00:02:03.994: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2284): libfprint-device-DEBUG: 00:02:03.994: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 146s (process:2284): libfprint-device-DEBUG: 00:02:03.994: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (process:2284): libfprint-virtual_image-DEBUG: 00:02:03.995: 31214368: ../libfprint/drivers/virtual-image.c:244 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.095: Image device close completed 146s (process:2284): libfprint-device-DEBUG: 00:02:04.095: Device reported close completion 146s (process:2284): libfprint-device-DEBUG: 00:02:04.095: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 146s (process:2284): libfprint-device-DEBUG: 00:02:04.095: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s Capture operation finished 146s Capture cancelled as expected 146s ok 146s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:2284): libfprint-virtual_image-DEBUG: 00:02:04.095: 31314827: ../libfprint/drivers/virtual-image.c:216 146s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:02:04.095: 31314835: ../libfprint/drivers/virtual-device-listener.c:153 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.195: Image device open completed 146s (process:2284): libfprint-device-DEBUG: 00:02:04.195: Device reported open completion 146s (process:2284): libfprint-device-DEBUG: 00:02:04.195: Completing action FPI_DEVICE_ACTION_OPEN in idle! 146s (process:2284): libfprint-device-DEBUG: 00:02:04.195: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (process:2284): libfprint-device-DEBUG: 00:02:04.196: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.196: Activating image device 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.196: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.196: Image device activation completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.196: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.196: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 146s (process:2284): libfprint-device-DEBUG: 00:02:04.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:02:04.197: Got a new connection! 146s (process:2284): libfprint-virtual_image-DEBUG: 00:02:04.197: image data: 0x39a2830 146s (process:2284): libfprint-device-DEBUG: 00:02:04.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.197: Image device reported finger status: on 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.197: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.197: Image device captured an image 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.197: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 146s (process:2284): libfprint-device-DEBUG: 00:02:04.197: Device reported finger status change: FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-device-DEBUG: 00:02:04.197: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.197: Image device reported finger status: off 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.197: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image-DEBUG: 00:02:04.223: Minutiae scan completed in 0.025774 secs 146s (process:2284): libfprint-device-DEBUG: 00:02:04.223: Device reported enroll progress, reported 1 of 5 have been completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.223: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 146s (process:2284): libfprint-device-DEBUG: 00:02:04.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2284): libfprint-device-DEBUG: 00:02:04.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.223: Image device reported finger status: on 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.223: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 146s (process:2284): libfprint-virtual_image-DEBUG: 00:02:04.223: image data: 0x39a2830 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.223: Image device captured an image 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.230: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 146s (process:2284): libfprint-device-DEBUG: 00:02:04.230: Device reported finger status change: FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-image-DEBUG: 00:02:04.249: Minutiae scan completed in 0.025821 secs 146s (process:2284): libfprint-device-DEBUG: 00:02:04.249: Device reported enroll progress, reported 2 of 5 have been completed 146s (process:2284): libfprint-device-DEBUG: 00:02:04.249: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device reported finger status: off 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 146s (process:2284): libfprint-device-DEBUG: 00:02:04.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2284): libfprint-virtual_image-DEBUG: 00:02:04.249: image data: 0x39b1090 146s (process:2284): libfprint-device-DEBUG: 00:02:04.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device reported finger status: on 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device captured an image 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 146s (process:2284): libfprint-device-DEBUG: 00:02:04.249: Device reported finger status change: FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-device-DEBUG: 00:02:04.249: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device reported finger status: off 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image-DEBUG: 00:02:04.274: Minutiae scan completed in 0.025399 secs 146s (process:2284): libfprint-device-DEBUG: 00:02:04.274: Device reported enroll progress, reported 3 of 5 have been completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.274: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 146s (process:2284): libfprint-device-DEBUG: 00:02:04.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2284): libfprint-virtual_image-DEBUG: 00:02:04.274: image data: 0x39a2830 146s (process:2284): libfprint-device-DEBUG: 00:02:04.275: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.275: Image device reported finger status: on 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.275: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.275: Image device captured an image 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.275: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 146s (process:2284): libfprint-device-DEBUG: 00:02:04.275: Device reported finger status change: FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-device-DEBUG: 00:02:04.275: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.275: Image device reported finger status: off 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.275: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image-DEBUG: 00:02:04.300: Minutiae scan completed in 0.025447 secs 146s (process:2284): libfprint-device-DEBUG: 00:02:04.300: Device reported enroll progress, reported 4 of 5 have been completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 146s (process:2284): libfprint-device-DEBUG: 00:02:04.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2284): libfprint-virtual_image-DEBUG: 00:02:04.300: image data: 0x39a2830 146s (process:2284): libfprint-device-DEBUG: 00:02:04.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.300: Image device reported finger status: on 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.300: Image device captured an image 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 146s (process:2284): libfprint-device-DEBUG: 00:02:04.300: Device reported finger status change: FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-device-DEBUG: 00:02:04.300: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.300: Image device reported finger status: off 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image-DEBUG: 00:02:04.326: Minutiae scan completed in 0.025451 secs 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Device reported enroll progress, reported 5 of 5 have been completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Deactivating image device 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device deactivation completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Device reported enroll completion 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Print for finger FP_FINGER_LEFT_THUMB enrolled 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Activating image device 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device activation completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2284): libfprint-virtual_image-DEBUG: 00:02:04.326: image data: 0x39b10c0 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device reported finger status: on 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device captured an image 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Device reported finger status change: FP_FINGER_STATUS_PRESENT 146s (process:2284): libfprint-device-DEBUG: 00:02:04.326: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device reported finger status: off 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Deactivating image device 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device deactivation completed 146s (process:2284): libfprint-image_device-DEBUG: 00:02:04.326: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 146s (process:2284): libfprint-image-DEBUG: 00:02:04.352: Minutiae scan completed in 0.025302 secs 148s (process:2284): libfprint-print-DEBUG: 00:02:05.456: score 1093/40 148s (process:2284): libfprint-device-DEBUG: 00:02:05.456: Device reported verify result 148s (process:2284): libfprint-device-DEBUG: 00:02:05.456: Device reported verify completion 148s (process:2284): libfprint-device-DEBUG: 00:02:05.456: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 148s (process:2284): libfprint-device-DEBUG: 00:02:05.456: Updated temperature model after 1.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 148s (process:2284): libfprint-device-DEBUG: 00:02:05.457: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Activating image device 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device activation completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 148s (process:2284): libfprint-device-DEBUG: 00:02:05.457: Device reported finger status change: FP_FINGER_STATUS_NEEDED 148s (process:2284): libfprint-virtual_image-DEBUG: 00:02:05.457: image data: 0x39c08a0 148s (process:2284): libfprint-device-DEBUG: 00:02:05.457: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device reported finger status: on 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device captured an image 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 148s (process:2284): libfprint-device-DEBUG: 00:02:05.457: Device reported finger status change: FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-device-DEBUG: 00:02:05.457: Device reported finger status change: FP_FINGER_STATUS_NONE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device reported finger status: off 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Deactivating image device 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device deactivation completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.457: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 148s (process:2284): libfprint-image-DEBUG: 00:02:05.480: Minutiae scan completed in 0.022912 secs 148s (process:2284): libfprint-print-DEBUG: 00:02:05.486: score 10/40 148s (process:2284): libfprint-print-DEBUG: 00:02:05.493: score 10/40 148s (process:2284): libfprint-print-DEBUG: 00:02:05.499: score 10/40 148s (process:2284): libfprint-print-DEBUG: 00:02:05.505: score 10/40 148s (process:2284): libfprint-print-DEBUG: 00:02:05.511: score 10/40 148s (process:2284): libfprint-device-DEBUG: 00:02:05.511: Device reported verify result 148s (process:2284): libfprint-device-DEBUG: 00:02:05.511: Device reported verify completion 148s (process:2284): libfprint-device-DEBUG: 00:02:05.511: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 148s (process:2284): libfprint-device-DEBUG: 00:02:05.511: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 148s (process:2284): libfprint-device-DEBUG: 00:02:05.511: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.511: Activating image device 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.511: Image device activation completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 148s (process:2284): libfprint-device-DEBUG: 00:02:05.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED 148s (process:2284): libfprint-virtual_image-DEBUG: 00:02:05.511: image data: 0x39cf8b0 148s (process:2284): libfprint-device-DEBUG: 00:02:05.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.511: Image device reported finger status: on 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.511: Image device captured an image 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.520: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 148s (process:2284): libfprint-device-DEBUG: 00:02:05.520: Device reported finger status change: FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-device-DEBUG: 00:02:05.520: Device reported finger status change: FP_FINGER_STATUS_NONE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.520: Image device reported finger status: off 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.520: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image-DEBUG: 00:02:05.534: Minutiae scan completed in 0.022841 secs 148s (process:2284): libfprint-device-DEBUG: 00:02:05.534: Device reported enroll progress, reported 1 of 5 have been completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.534: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 148s (process:2284): libfprint-device-DEBUG: 00:02:05.534: Device reported finger status change: FP_FINGER_STATUS_NEEDED 148s (process:2284): libfprint-device-DEBUG: 00:02:05.534: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.534: Image device reported finger status: on 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.534: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 148s (process:2284): libfprint-virtual_image-DEBUG: 00:02:05.534: image data: 0x39de8c0 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.534: Image device captured an image 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.534: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 148s (process:2284): libfprint-device-DEBUG: 00:02:05.534: Device reported finger status change: FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-image-DEBUG: 00:02:05.557: Minutiae scan completed in 0.022395 secs 148s (process:2284): libfprint-device-DEBUG: 00:02:05.557: Device reported enroll progress, reported 2 of 5 have been completed 148s (process:2284): libfprint-device-DEBUG: 00:02:05.557: Device reported finger status change: FP_FINGER_STATUS_NONE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device reported finger status: off 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 148s (process:2284): libfprint-device-DEBUG: 00:02:05.557: Device reported finger status change: FP_FINGER_STATUS_NEEDED 148s (process:2284): libfprint-virtual_image-DEBUG: 00:02:05.557: image data: 0x39cf8b0 148s (process:2284): libfprint-device-DEBUG: 00:02:05.557: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device reported finger status: on 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device captured an image 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 148s (process:2284): libfprint-device-DEBUG: 00:02:05.557: Device reported finger status change: FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-device-DEBUG: 00:02:05.557: Device reported finger status change: FP_FINGER_STATUS_NONE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device reported finger status: off 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.557: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image-DEBUG: 00:02:05.580: Minutiae scan completed in 0.022655 secs 148s (process:2284): libfprint-device-DEBUG: 00:02:05.580: Device reported enroll progress, reported 3 of 5 have been completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.580: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 148s (process:2284): libfprint-device-DEBUG: 00:02:05.580: Device reported finger status change: FP_FINGER_STATUS_NEEDED 148s (process:2284): libfprint-virtual_image-DEBUG: 00:02:05.580: image data: 0x39cf8b0 148s (process:2284): libfprint-device-DEBUG: 00:02:05.580: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.580: Image device reported finger status: on 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.580: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.580: Image device captured an image 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.580: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 148s (process:2284): libfprint-device-DEBUG: 00:02:05.580: Device reported finger status change: FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-device-DEBUG: 00:02:05.580: Device reported finger status change: FP_FINGER_STATUS_NONE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.580: Image device reported finger status: off 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.580: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image-DEBUG: 00:02:05.602: Minutiae scan completed in 0.022397 secs 148s (process:2284): libfprint-device-DEBUG: 00:02:05.602: Device reported enroll progress, reported 4 of 5 have been completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.602: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 148s (process:2284): libfprint-device-DEBUG: 00:02:05.602: Device reported finger status change: FP_FINGER_STATUS_NEEDED 148s (process:2284): libfprint-virtual_image-DEBUG: 00:02:05.602: image data: 0x39cf8b0 148s (process:2284): libfprint-device-DEBUG: 00:02:05.602: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.602: Image device reported finger status: on 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.602: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.602: Image device captured an image 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.610: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 148s (process:2284): libfprint-device-DEBUG: 00:02:05.610: Device reported finger status change: FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-device-DEBUG: 00:02:05.610: Device reported finger status change: FP_FINGER_STATUS_NONE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.610: Image device reported finger status: off 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.610: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image-DEBUG: 00:02:05.625: Minutiae scan completed in 0.023022 secs 148s (process:2284): libfprint-device-DEBUG: 00:02:05.625: Device reported enroll progress, reported 5 of 5 have been completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.625: Deactivating image device 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.625: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.625: Image device deactivation completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.625: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 148s (process:2284): libfprint-device-DEBUG: 00:02:05.625: Device reported enroll completion 148s (process:2284): libfprint-device-DEBUG: 00:02:05.625: Print for finger FP_FINGER_LEFT_THUMB enrolled 148s (process:2284): libfprint-device-DEBUG: 00:02:05.626: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 148s (process:2284): libfprint-device-DEBUG: 00:02:05.626: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 148s (process:2284): libfprint-device-DEBUG: 00:02:05.626: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Activating image device 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device activation completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 148s (process:2284): libfprint-device-DEBUG: 00:02:05.626: Device reported finger status change: FP_FINGER_STATUS_NEEDED 148s (process:2284): libfprint-virtual_image-DEBUG: 00:02:05.626: image data: 0x39b10c0 148s (process:2284): libfprint-device-DEBUG: 00:02:05.626: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device reported finger status: on 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device captured an image 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 148s (process:2284): libfprint-device-DEBUG: 00:02:05.626: Device reported finger status change: FP_FINGER_STATUS_PRESENT 148s (process:2284): libfprint-device-DEBUG: 00:02:05.626: Device reported finger status change: FP_FINGER_STATUS_NONE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device reported finger status: off 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Deactivating image device 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device deactivation completed 148s (process:2284): libfprint-image_device-DEBUG: 00:02:05.626: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 148s (process:2284): libfprint-image-DEBUG: 00:02:05.651: Minutiae scan completed in 0.025108 secs 149s (process:2284): libfprint-print-DEBUG: 00:02:06.746: score 1093/40 149s (process:2284): libfprint-device-DEBUG: 00:02:06.746: Device reported verify result 149s (process:2284): libfprint-device-DEBUG: 00:02:06.746: Device reported verify completion 149s (process:2284): libfprint-device-DEBUG: 00:02:06.746: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:06.746: Updated temperature model after 1.12 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-device-DEBUG: 00:02:06.746: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.746: Activating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.746: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.746: Image device activation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.746: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.746: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:06.746: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:06.747: image data: 0x39c08a0 149s (process:2284): libfprint-device-DEBUG: 00:02:06.747: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:06.747: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:06.747: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Deactivating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device deactivation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:06.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 149s (process:2284): libfprint-image-DEBUG: 00:02:06.769: Minutiae scan completed in 0.022509 secs 149s (process:2284): libfprint-print-DEBUG: 00:02:06.776: score 10/40 149s (process:2284): libfprint-print-DEBUG: 00:02:06.782: score 10/40 149s (process:2284): libfprint-print-DEBUG: 00:02:06.788: score 10/40 149s (process:2284): libfprint-print-DEBUG: 00:02:06.794: score 10/40 149s (process:2284): libfprint-print-DEBUG: 00:02:06.800: score 10/40 149s (process:2284): libfprint-print-DEBUG: 00:02:07.020: score 855/40 149s (process:2284): libfprint-device-DEBUG: 00:02:07.020: Device reported verify result 149s (process:2284): libfprint-device-DEBUG: 00:02:07.020: Device reported verify completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.020: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.020: Updated temperature model after 0.27 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-device-DEBUG: 00:02:07.020: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Activating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device activation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Device reported verify result 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Deactivating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device deactivation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Device reported verify completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Activating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device activation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Deactivating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device deactivation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Device reported verify completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.021: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.021: 34240859: ../libfprint/drivers/virtual-image.c:244 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.121: Image device close completed 149s (process:2284): libfprint-device-DEBUG: 00:02:07.121: Device reported close completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.121: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.121: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s Print was processed, continuing 149s Print was processed, continuing 149s Print was processed, continuing 149s Print was processed, continuing 149s Print was processed, continuing 149s Enroll done 149s Print was processed, continuing 149s Print was processed, continuing 149s Print was processed, continuing 149s Print was processed, continuing 149s Print was processed, continuing 149s Enroll done 149s fp - device - error - quark: An unspecified error occurred! (0) 149s ok 149s test_features (__main__.VirtualImage.test_features) ... (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.122: 34341344: ../libfprint/drivers/virtual-image.c:216 149s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:02:07.122: 34341357: ../libfprint/drivers/virtual-device-listener.c:153 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.221: Image device open completed 149s (process:2284): libfprint-device-DEBUG: 00:02:07.221: Device reported open completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.221: Completing action FPI_DEVICE_ACTION_OPEN in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.221: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.222: 34441545: ../libfprint/drivers/virtual-image.c:244 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.322: Image device close completed 149s (process:2284): libfprint-device-DEBUG: 00:02:07.322: Device reported close completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.322: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.322: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s ok 149s test_identify (__main__.VirtualImage.test_identify) ... (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.322: 34541770: ../libfprint/drivers/virtual-image.c:216 149s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:02:07.322: 34541780: ../libfprint/drivers/virtual-device-listener.c:153 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.422: Image device open completed 149s (process:2284): libfprint-device-DEBUG: 00:02:07.422: Device reported open completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.422: Completing action FPI_DEVICE_ACTION_OPEN in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.422: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-device-DEBUG: 00:02:07.422: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.422: Activating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.422: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.422: Image device activation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.422: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.422: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.422: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:02:07.423: Got a new connection! 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.423: image data: 0x39b10c0 149s (process:2284): libfprint-device-DEBUG: 00:02:07.423: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.423: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.423: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.423: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.423: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.423: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image-DEBUG: 00:02:07.448: Minutiae scan completed in 0.025145 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.448: Device reported enroll progress, reported 1 of 5 have been completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.448: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-device-DEBUG: 00:02:07.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.448: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.448: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.448: image data: 0x39b10c0 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.448: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.448: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.448: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image-DEBUG: 00:02:07.473: Minutiae scan completed in 0.025038 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.473: Device reported enroll progress, reported 2 of 5 have been completed 149s (process:2284): libfprint-device-DEBUG: 00:02:07.473: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.473: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.473: image data: 0x39b10c0 149s (process:2284): libfprint-device-DEBUG: 00:02:07.473: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.473: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.473: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.473: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image-DEBUG: 00:02:07.499: Minutiae scan completed in 0.025040 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.499: Device reported enroll progress, reported 3 of 5 have been completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.499: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.499: image data: 0x39b10c0 149s (process:2284): libfprint-device-DEBUG: 00:02:07.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.499: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.499: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.499: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.499: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.499: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.500: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.500: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.500: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image-DEBUG: 00:02:07.524: Minutiae scan completed in 0.025107 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.524: Device reported enroll progress, reported 4 of 5 have been completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.524: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.524: image data: 0x39b10c0 149s (process:2284): libfprint-device-DEBUG: 00:02:07.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.524: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.524: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.524: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.530: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.530: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.530: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.530: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.530: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image-DEBUG: 00:02:07.549: Minutiae scan completed in 0.025117 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.549: Device reported enroll progress, reported 5 of 5 have been completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.549: Deactivating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.549: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.549: Image device deactivation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.549: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 149s (process:2284): libfprint-device-DEBUG: 00:02:07.549: Device reported enroll completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.549: Print for finger FP_FINGER_LEFT_THUMB enrolled 149s (process:2284): libfprint-device-DEBUG: 00:02:07.549: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.549: Updated temperature model after 0.13 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-device-DEBUG: 00:02:07.550: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Activating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device activation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.550: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.550: image data: 0x39dd990 149s (process:2284): libfprint-device-DEBUG: 00:02:07.550: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.550: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.550: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.550: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image-DEBUG: 00:02:07.573: Minutiae scan completed in 0.023320 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.573: Device reported enroll progress, reported 1 of 5 have been completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.573: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.573: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-device-DEBUG: 00:02:07.573: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.573: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.573: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.573: image data: 0x39c08a0 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.573: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.573: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.573: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image-DEBUG: 00:02:07.596: Minutiae scan completed in 0.022649 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.596: Device reported enroll progress, reported 2 of 5 have been completed 149s (process:2284): libfprint-device-DEBUG: 00:02:07.596: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.596: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.596: image data: 0x39c08a0 149s (process:2284): libfprint-device-DEBUG: 00:02:07.596: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.596: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.596: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.596: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image-DEBUG: 00:02:07.619: Minutiae scan completed in 0.022358 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.619: Device reported enroll progress, reported 3 of 5 have been completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.619: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.619: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.619: image data: 0x39c08a0 149s (process:2284): libfprint-device-DEBUG: 00:02:07.619: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.619: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.619: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.619: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.619: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.619: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.619: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.619: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.619: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image-DEBUG: 00:02:07.641: Minutiae scan completed in 0.022416 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.642: Device reported enroll progress, reported 4 of 5 have been completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.642: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.642: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.642: image data: 0x39c08a0 149s (process:2284): libfprint-device-DEBUG: 00:02:07.642: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.642: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.642: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.642: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.650: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.650: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.650: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.650: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.650: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image-DEBUG: 00:02:07.664: Minutiae scan completed in 0.022496 secs 149s (process:2284): libfprint-device-DEBUG: 00:02:07.664: Device reported enroll progress, reported 5 of 5 have been completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.664: Deactivating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.664: Image device deactivation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 149s (process:2284): libfprint-device-DEBUG: 00:02:07.664: Device reported enroll completion 149s (process:2284): libfprint-device-DEBUG: 00:02:07.664: Print for finger FP_FINGER_LEFT_THUMB enrolled 149s (process:2284): libfprint-device-DEBUG: 00:02:07.664: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 149s (process:2284): libfprint-device-DEBUG: 00:02:07.664: Updated temperature model after 0.11 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-device-DEBUG: 00:02:07.665: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Activating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device activation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 149s (process:2284): libfprint-device-DEBUG: 00:02:07.665: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.665: image data: 0x39cf8b0 149s (process:2284): libfprint-device-DEBUG: 00:02:07.665: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device reported finger status: on 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device captured an image 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 149s (process:2284): libfprint-device-DEBUG: 00:02:07.665: Device reported finger status change: FP_FINGER_STATUS_PRESENT 149s (process:2284): libfprint-device-DEBUG: 00:02:07.665: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device reported finger status: off 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Deactivating image device 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device deactivation completed 149s (process:2284): libfprint-image_device-DEBUG: 00:02:07.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 150s (process:2284): libfprint-image-DEBUG: 00:02:07.687: Minutiae scan completed in 0.022452 secs 150s (process:2284): libfprint-print-DEBUG: 00:02:07.694: score 10/40 150s (process:2284): libfprint-print-DEBUG: 00:02:07.700: score 10/40 150s (process:2284): libfprint-print-DEBUG: 00:02:07.706: score 10/40 150s (process:2284): libfprint-print-DEBUG: 00:02:07.712: score 10/40 150s (process:2284): libfprint-print-DEBUG: 00:02:07.718: score 10/40 150s (process:2284): libfprint-print-DEBUG: 00:02:07.939: score 855/40 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Device reported identify result 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Device reported identify completion 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Updated temperature model after 0.28 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Activating image device 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device activation completed 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Device reported finger status change: FP_FINGER_STATUS_NEEDED 150s (process:2284): libfprint-virtual_image-DEBUG: 00:02:07.940: image data: 0x39bf940 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device reported finger status: on 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device captured an image 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Device reported finger status change: FP_FINGER_STATUS_PRESENT 150s (process:2284): libfprint-device-DEBUG: 00:02:07.940: Device reported finger status change: FP_FINGER_STATUS_NONE 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device reported finger status: off 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Deactivating image device 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device deactivation completed 150s (process:2284): libfprint-image_device-DEBUG: 00:02:07.940: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 150s (process:2284): libfprint-image-DEBUG: 00:00:42.265: Minutiae scan completed in 0.026605 secs 151s Executing: libfprint-2/virtual-image.test 151s (process:2284): libfprint-print-DEBUG: 00:00:43.360: score 1093/40 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported identify result 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported identify completion 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Updated temperature model after 1.12 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Activating image device 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device activation completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported identify result 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Deactivating image device 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device deactivation completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported identify completion 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Activating image device 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device activation completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Deactivating image device 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device deactivation completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported identify completion 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 151s (process:2284): libfprint-device-DEBUG: 00:00:43.360: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-virtual_image-DEBUG: 00:00:43.361: 36282411: ../libfprint/drivers/virtual-image.c:244 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.461: Image device close completed 151s (process:2284): libfprint-device-DEBUG: 00:00:43.461: Device reported close completion 151s (process:2284): libfprint-device-DEBUG: 00:00:43.461: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 151s (process:2284): libfprint-device-DEBUG: 00:00:43.461: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s Print was processed, continuing 151s Print was processed, continuing 151s Print was processed, continuing 151s Print was processed, continuing 151s Print was processed, continuing 151s Enroll done 151s Print was processed, continuing 151s Print was processed, continuing 151s Print was processed, continuing 151s Print was processed, continuing 151s Print was processed, continuing 151s Enroll done 151s Identify finished 151s Identify finished 151s Identify finished 151s fp - device - retry - quark: The swipe was too short, please try again. (1) 151s Identify finished 151s fp - device - error - quark: An unspecified error occurred! (0) 151s ok 151s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:2284): libfprint-virtual_image-DEBUG: 00:00:43.461: 36382848: ../libfprint/drivers/virtual-image.c:216 151s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:00:43.461: 36382861: ../libfprint/drivers/virtual-device-listener.c:153 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.561: Image device open completed 151s (process:2284): libfprint-device-DEBUG: 00:00:43.561: Device reported open completion 151s (process:2284): libfprint-device-DEBUG: 00:00:43.561: Completing action FPI_DEVICE_ACTION_OPEN in idle! 151s (process:2284): libfprint-device-DEBUG: 00:00:43.561: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-device-DEBUG: 00:00:43.561: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.561: Activating image device 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.561: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.561: Image device activation completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.561: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.561: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:2284): libfprint-device-DEBUG: 00:00:43.561: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:2284): libfprint-virtual_device_connection-DEBUG: 00:00:43.561: Got a new connection! 151s (process:2284): libfprint-virtual_image-DEBUG: 00:00:43.561: image data: 0x39bf940 151s (process:2284): libfprint-device-DEBUG: 00:00:43.562: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.562: Image device reported finger status: on 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.562: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.562: Image device captured an image 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.562: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 151s (process:2284): libfprint-device-DEBUG: 00:00:43.562: Device reported finger status change: FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-device-DEBUG: 00:00:43.562: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.562: Image device reported finger status: off 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.562: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image-DEBUG: 00:00:43.587: Minutiae scan completed in 0.025324 secs 151s (process:2284): libfprint-device-DEBUG: 00:00:43.587: Device reported enroll progress, reported 1 of 5 have been completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.587: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:2284): libfprint-device-DEBUG: 00:00:43.587: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:2284): libfprint-device-DEBUG: 00:00:43.587: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.587: Image device reported finger status: on 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.587: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 151s (process:2284): libfprint-virtual_image-DEBUG: 00:00:43.587: image data: 0x39bf940 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.587: Image device captured an image 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.587: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 151s (process:2284): libfprint-device-DEBUG: 00:00:43.587: Device reported finger status change: FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-image-DEBUG: 00:00:43.612: Minutiae scan completed in 0.025092 secs 151s (process:2284): libfprint-device-DEBUG: 00:00:43.613: Device reported enroll progress, reported 2 of 5 have been completed 151s (process:2284): libfprint-device-DEBUG: 00:00:43.613: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device reported finger status: off 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:2284): libfprint-device-DEBUG: 00:00:43.613: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:2284): libfprint-virtual_image-DEBUG: 00:00:43.613: image data: 0x39bf940 151s (process:2284): libfprint-device-DEBUG: 00:00:43.613: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device reported finger status: on 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device captured an image 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 151s (process:2284): libfprint-device-DEBUG: 00:00:43.613: Device reported finger status change: FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-device-DEBUG: 00:00:43.613: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device reported finger status: off 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.613: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image-DEBUG: 00:00:43.638: Minutiae scan completed in 0.025251 secs 151s (process:2284): libfprint-device-DEBUG: 00:00:43.638: Device reported enroll progress, reported 3 of 5 have been completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.638: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:2284): libfprint-device-DEBUG: 00:00:43.638: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:2284): libfprint-virtual_image-DEBUG: 00:00:43.638: image data: 0x39bf940 151s (process:2284): libfprint-device-DEBUG: 00:00:43.638: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.638: Image device reported finger status: on 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.638: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.638: Image device captured an image 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.638: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 151s (process:2284): libfprint-device-DEBUG: 00:00:43.648: Device reported finger status change: FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-device-DEBUG: 00:00:43.648: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.648: Image device reported finger status: off 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.648: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image-DEBUG: 00:00:43.664: Minutiae scan completed in 0.025212 secs 151s (process:2284): libfprint-device-DEBUG: 00:00:43.664: Device reported enroll progress, reported 4 of 5 have been completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:2284): libfprint-device-DEBUG: 00:00:43.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:2284): libfprint-virtual_image-DEBUG: 00:00:43.664: image data: 0x39ce1a0 151s (process:2284): libfprint-device-DEBUG: 00:00:43.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.664: Image device reported finger status: on 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.664: Image device captured an image 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 151s (process:2284): libfprint-device-DEBUG: 00:00:43.664: Device reported finger status change: FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-device-DEBUG: 00:00:43.664: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.664: Image device reported finger status: off 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.664: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image-DEBUG: 00:00:43.689: Minutiae scan completed in 0.025237 secs 151s (process:2284): libfprint-device-DEBUG: 00:00:43.689: Device reported enroll progress, reported 5 of 5 have been completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.689: Deactivating image device 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.689: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.689: Image device deactivation completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.689: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 151s (process:2284): libfprint-device-DEBUG: 00:00:43.689: Device reported enroll completion 151s (process:2284): libfprint-device-DEBUG: 00:00:43.689: Print for finger FP_FINGER_LEFT_THUMB enrolled 151s (process:2284): libfprint-device-DEBUG: 00:00:43.689: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 151s (process:2284): libfprint-device-DEBUG: 00:00:43.689: Updated temperature model after 0.13 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-device-DEBUG: 00:00:43.690: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Activating image device 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device activation completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:2284): libfprint-device-DEBUG: 00:00:43.690: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:2284): libfprint-virtual_image-DEBUG: 00:00:43.690: image data: 0x39dca00 151s (process:2284): libfprint-device-DEBUG: 00:00:43.690: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device reported finger status: on 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device captured an image 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 151s (process:2284): libfprint-device-DEBUG: 00:00:43.690: Device reported finger status change: FP_FINGER_STATUS_PRESENT 151s (process:2284): libfprint-device-DEBUG: 00:00:43.690: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device reported finger status: off 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Deactivating image device 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device deactivation completed 151s (process:2284): libfprint-image_device-DEBUG: 00:00:43.690: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 151s (process:2284): libfprint-image-DEBUG: 00:00:43.715: Minutiae scan completed in 0.025179 secs 152s (process:2284): libfprint-print-DEBUG: 00:00:44.800: score 1093/40 152s (process:2284): libfprint-device-DEBUG: 00:00:44.801: Device reported verify result 152s (process:2284): libfprint-device-DEBUG: 00:00:44.801: Device reported verify completion 152s (process:2284): libfprint-device-DEBUG: 00:00:44.801: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 152s (process:2284): libfprint-device-DEBUG: 00:00:44.801: Updated temperature model after 1.11 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:2284): libfprint-device-DEBUG: 00:00:44.801: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.801: Activating image device 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.801: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.801: Image device activation completed 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.801: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.801: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 152s (process:2284): libfprint-device-DEBUG: 00:00:44.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:2284): libfprint-virtual_image-DEBUG: 00:00:44.801: image data: 0x39c1210 152s (process:2284): libfprint-device-DEBUG: 00:00:44.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.801: Image device reported finger status: on 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.801: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.801: Image device captured an image 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.808: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 152s (process:2284): libfprint-device-DEBUG: 00:00:44.808: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:2284): libfprint-device-DEBUG: 00:00:44.808: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.808: Image device reported finger status: off 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.808: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.808: Deactivating image device 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.808: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.808: Image device deactivation completed 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.808: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 152s (process:2284): libfprint-image-DEBUG: 00:00:44.824: Minutiae scan completed in 0.022561 secs 152s (process:2284): libfprint-print-DEBUG: 00:00:44.830: score 10/40 152s (process:2284): libfprint-print-DEBUG: 00:00:44.836: score 10/40 152s (process:2284): libfprint-print-DEBUG: 00:00:44.843: score 10/40 152s (process:2284): libfprint-print-DEBUG: 00:00:44.849: score 10/40 152s (process:2284): libfprint-print-DEBUG: 00:00:44.855: score 10/40 152s (process:2284): libfprint-device-DEBUG: 00:00:44.855: Device reported verify result 152s (process:2284): libfprint-device-DEBUG: 00:00:44.855: Device reported verify completion 152s (process:2284): libfprint-device-DEBUG: 00:00:44.855: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 152s (process:2284): libfprint-device-DEBUG: 00:00:44.855: Updated temperature model after 0.05 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:2284): libfprint-virtual_image-DEBUG: 00:00:44.855: 37776680: ../libfprint/drivers/virtual-image.c:244 152s (process:2284): libfprint-image_device-DEBUG: 00:00:44.955: Image device close completed 152s (process:2284): libfprint-device-DEBUG: 00:00:44.955: Device reported close completion 152s (process:2284): libfprint-device-DEBUG: 00:00:44.955: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 152s (process:2284): libfprint-device-DEBUG: 00:00:44.955: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s Print was processed, continuing 152s Print was processed, continuing 152s Print was processed, continuing 152s Print was processed, continuing 152s Print was processed, continuing 152s Enroll done 152s ok 152s 152s ---------------------------------------------------------------------- 152s Ran 5 tests in 6.772s 152s 152s OK 152s PASS: libfprint-2/virtual-image.test 153s Running test: libfprint-2/fpi-ssm.test 153s TAP version 14 153s # random seed: R02S329d97f28462b936267f955a566f27b0 153s 1..42 153s # Start of ssm tests 153s ok 1 /ssm/new 153s ok 2 /ssm/set_data 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s ok 3 /ssm/start 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 4 /ssm/next 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 5 /ssm/jump_to_state 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 153s ok 6 /ssm/mark_completed 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # 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. 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 153s ok 7 /ssm/mark_failed 153s # Start of new tests 153s ok 8 /ssm/new/full 153s ok 9 /ssm/new/no_handler 153s ok 10 /ssm/new/wrong_states 153s # End of new tests 153s # Start of set_data tests 153s ok 11 /ssm/set_data/cleanup 153s # End of set_data tests 153s # Start of start tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully 153s ok 12 /ssm/start/single 153s # End of start tests 153s # Start of next tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 153s ok 13 /ssm/next/complete 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 14 /ssm/next/not_started 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 15 /ssm/next/with_delayed 153s # End of next tests 153s # Start of jump_to_state tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 153s ok 16 /ssm/jump_to_state/not_started 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 153s ok 17 /ssm/jump_to_state/with_delayed 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 153s ok 18 /ssm/jump_to_state/last 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 153s ok 19 /ssm/jump_to_state/wrong 153s # End of jump_to_state tests 153s # Start of mark_completed tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 153s ok 20 /ssm/mark_completed/not_started 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 153s ok 21 /ssm/mark_completed/with_delayed 153s # End of mark_completed tests 153s # Start of mark_failed tests 153s # 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. 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 153s ok 22 /ssm/mark_failed/not_started 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # 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. 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 153s ok 23 /ssm/mark_failed/with_delayed 153s # End of mark_failed tests 153s # Start of delayed tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 24 /ssm/delayed/next 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 25 /ssm/delayed/jump_to_state 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 153s ok 26 /ssm/delayed/mark_completed 153s # Start of next tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 153s ok 27 /ssm/delayed/next/cancel 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 28 /ssm/delayed/next/not_started 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 153s ok 29 /ssm/delayed/next/complete 153s # End of next tests 153s # Start of jump_to_state tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 153s ok 30 /ssm/delayed/jump_to_state/cancel 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 153s ok 31 /ssm/delayed/jump_to_state/not_started 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 153s ok 32 /ssm/delayed/jump_to_state/last 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 153s ok 33 /ssm/delayed/jump_to_state/wrong 153s # End of jump_to_state tests 153s # Start of mark_completed tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 153s ok 34 /ssm/delayed/mark_completed/cancel 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 153s ok 35 /ssm/delayed/mark_completed/not_started 153s # End of mark_completed tests 153s # Start of cancel tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 153s ok 36 /ssm/delayed/cancel/error 153s # End of cancel tests 153s # End of delayed tests 153s # Start of subssm tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 37 /ssm/subssm/start 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 153s # 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. 153s # 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. 153s # 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. 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 153s ok 38 /ssm/subssm/mark_failed 153s # Start of start tests 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 153s ok 39 /ssm/subssm/start/with_started 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 153s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 154s ok 40 /ssm/subssm/start/with_delayed 154s # End of start tests 154s # End of subssm tests 154s # Start of cleanup tests 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 154s ok 41 /ssm/cleanup/complete 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 154s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 154s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup 154s ok 42 /ssm/cleanup/fail 154s # End of cleanup tests 154s # End of ssm tests 154s PASS: libfprint-2/fpi-ssm.test 154s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 154s TAP version 14 154s # random seed: R02S0ebe385654531589841b499546809d6e 154s 1..4 154s # Start of context tests 154s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 154s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 154s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffaf0029d0, GType is 2929571776048 154s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 154s ok 1 /context/new 154s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 154s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 154s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 154s ok 2 /context/no-devices 154s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 154s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 154s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffaf0029d0, GType is 2929571776048 154s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 154s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 154s # libfprint-context-DEBUG: created 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 154s # 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 3 /context/has-virtual-device 154s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 154s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 154s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffaf0029d0, GType is 2929571776048 154s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 154s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 154s # libfprint-context-DEBUG: created 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 154s # 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 4 /context/enumerates-new-devices 154s # End of context tests 154s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 154s Running test: libfprint-2/fpi-device.test 154s TAP version 14 154s # random seed: R02Sac090c967e6c7a0dc03afe02defb980d 154s 1..97 154s # Start of driver tests 154s ok 1 /driver/get_driver 154s ok 2 /driver/get_device_id 154s ok 3 /driver/get_name 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 4 /driver/is_open 154s ok 5 /driver/get_nr_enroll_stages 154s ok 6 /driver/set_nr_enroll_stages 154s ok 7 /driver/supports_identify 154s ok 8 /driver/supports_capture 154s ok 9 /driver/has_storage 154s ok 10 /driver/do_not_support_identify 154s ok 11 /driver/do_not_support_capture 154s ok 12 /driver/has_not_storage 154s ok 13 /driver/get_usb_device 154s ok 14 /driver/get_virtual_env 154s ok 15 /driver/get_driver_data 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 154s # 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 16 /driver/initial_features 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 154s # 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 17 /driver/probe 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 18 /driver/open 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 19 /driver/close 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 154s # 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 20 /driver/enroll 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 21 /driver/verify 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 22 /driver/identify 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 154s # 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 23 /driver/capture 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 154s # 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 24 /driver/list 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 25 /driver/delete 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 26 /driver/clear_storage 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 27 /driver/cancel 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 28 /driver/critical 154s ok 29 /driver/get_current_action 154s ok 30 /driver/timeout 154s ok 31 /driver/error_types 154s ok 32 /driver/retry_error_types 154s # Start of get_scan_type tests 154s ok 33 /driver/get_scan_type/press 154s ok 34 /driver/get_scan_type/swipe 154s # End of get_scan_type tests 154s # Start of set_scan_type tests 154s ok 35 /driver/set_scan_type/press 154s ok 36 /driver/set_scan_type/swipe 154s # End of set_scan_type tests 154s # Start of finger_status tests 154s ok 37 /driver/finger_status/inactive 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 154s ok 38 /driver/finger_status/waiting 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 154s ok 39 /driver/finger_status/present 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 154s ok 40 /driver/finger_status/changes 154s # End of finger_status tests 154s # Start of features tests 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 154s # 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 41 /driver/features/probe_updates 154s # End of features tests 154s # Start of initial_features tests 154s ok 42 /driver/initial_features/none 154s ok 43 /driver/initial_features/no_capture 154s ok 44 /driver/initial_features/no_verify 154s ok 45 /driver/initial_features/no_identify 154s ok 46 /driver/initial_features/no_storage 154s ok 47 /driver/initial_features/no_list 154s ok 48 /driver/initial_features/no_delete 154s ok 49 /driver/initial_features/no_clear 154s # End of initial_features tests 154s # Start of probe tests 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 50 /driver/probe/error 154s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 51 /driver/probe/action_error 154s # End of probe tests 154s # Start of open tests 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 52 /driver/open/error 154s # End of open tests 154s # Start of close tests 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 53 /driver/close/error 154s # End of close tests 154s # Start of enroll tests 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 154s # 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 54 /driver/enroll/error 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported enroll progress, reported 713964222 of 290969843 have been completed 154s # libfprint-device-DEBUG: Device reported enroll progress, reported 1267689859 of 290969843 have been completed 154s # libfprint-device-DEBUG: Device reported enroll progress, reported 407290054 of 290969843 have been completed 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 154s # 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 55 /driver/enroll/progress 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 154s # 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 56 /driver/enroll/update_nbis 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 57 /driver/enroll/update_nbis_wrong_device 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 58 /driver/enroll/update_nbis_wrong_driver 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 59 /driver/enroll/update_nbis_missing_feature 154s # Start of error tests 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 60 /driver/enroll/error/no_print 154s # End of error tests 154s # End of enroll tests 154s # Start of verify tests 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 61 /driver/verify/fail 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 62 /driver/verify/retry 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 63 /driver/verify/error 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 64 /driver/verify/not_supported 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 65 /driver/verify/report_no_cb 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 66 /driver/verify/not_reported 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 67 /driver/verify/complete_retry 154s # End of verify tests 154s # Start of identify tests 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 154s ok 68 /driver/identify/fail 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 154s ok 69 /driver/identify/retry 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 154s ok 70 /driver/identify/error 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 71 /driver/identify/not_reported 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 72 /driver/identify/complete_retry 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 73 /driver/identify/report_no_cb 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 74 /driver/identify/suspend_continues 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 75 /driver/identify/suspend_succeeds 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 76 /driver/identify/suspend_busy_error 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 77 /driver/identify/suspend_while_idle 154s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 156s Executing: libfprint-2/fpi-device.test 156s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 156s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 156s # 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 156s # 156s # libfprint-device-DEBUG: Device reported identify completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 158s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 161s Executing: libfprint-2/fpi-device.test 161s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 78 /driver/identify/warmup_cooldown 161s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 161s # End of identify tests 161s # Start of capture tests 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 79 /driver/capture/not_supported 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 161s # 161s # libfprint-device-DEBUG: Device reported capture completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE 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_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s ok 80 /driver/capture/error 161s # End of capture tests 161s # Start of list tests 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 161s # 161s # libfprint-device-DEBUG: Device reported listing completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 81 /driver/list/error 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 82 /driver/list/no_storage 161s # End of list tests 161s # Start of delete tests 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 161s # 161s # libfprint-device-DEBUG: Device reported deletion completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 83 /driver/delete/error 161s # End of delete tests 161s # Start of clear_storage tests 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 161s # 161s # libfprint-device-DEBUG: Device reported deletion completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 84 /driver/clear_storage/error 161s # End of clear_storage tests 161s # Start of cancel tests 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 161s # 161s # libfprint-device-DEBUG: Device reported deletion completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 85 /driver/cancel/fail 161s # End of cancel tests 161s # Start of get_current_action tests 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 86 /driver/get_current_action/open 161s # End of get_current_action tests 161s # Start of get_cancellable tests 161s ok 87 /driver/get_cancellable/error 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 88 /driver/get_cancellable/open 161s # Start of open tests 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 89 /driver/get_cancellable/open/internal 161s # End of open tests 161s # End of get_cancellable tests 161s # Start of action_is_cancelled tests 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 90 /driver/action_is_cancelled/open 161s ok 91 /driver/action_is_cancelled/error 161s # Start of open tests 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 92 /driver/action_is_cancelled/open/internal 161s # End of open tests 161s # End of action_is_cancelled tests 161s # Start of complete_action tests 161s # Start of all tests 161s ok 93 /driver/complete_action/all/error 161s # End of all tests 161s # End of complete_action tests 161s # Start of action_error tests 161s ok 94 /driver/action_error/error 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 161s # libfprint-device-DEBUG: Device reported enroll completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL 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_WARM 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 161s # libfprint-device-DEBUG: Device reported verify completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 161s # libfprint-device-DEBUG: Device reported identify completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 161s # libfprint-device-DEBUG: Device reported capture completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 161s # libfprint-device-DEBUG: Device reported listing completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 161s # libfprint-device-DEBUG: Device reported deletion completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 161s # libfprint-device-DEBUG: Device reported deletion completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s ok 95 /driver/action_error/all 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 161s # 161s # libfprint-device-DEBUG: Device reported enroll completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL 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_WARM 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 161s # 161s # libfprint-device-DEBUG: Device reported verify completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 161s # 161s # libfprint-device-DEBUG: Device reported identify completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 161s # 161s # libfprint-device-DEBUG: Device reported capture completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 161s # 161s # libfprint-device-DEBUG: Device reported listing completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 161s # 161s # libfprint-device-DEBUG: Device reported deletion completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 161s # 161s # libfprint-device-DEBUG: Device reported deletion completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 161s ok 96 /driver/action_error/fail 161s # End of action_error tests 161s # Start of timeout tests 161s ok 97 /driver/timeout/cancelled 161s # End of timeout tests 161s # End of driver tests 161s PASS: libfprint-2/fpi-device.test 161s Running test: libfprint-2/fp-context.test 161s TAP version 14 161s # random seed: R02Sb5ca70940b5bdcde319aebb870279111 161s 1..9 161s # Start of context tests 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+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 ok 1 /context/new 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+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 ok 2 /context/no-devices 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 161s # libfprint-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-GYIC22/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 # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 161s ok 3 /context/has-virtual-device 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+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 # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LKNC22/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 # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 161s ok 4 /context/enumerates-new-devices 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 161s # libfprint-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-FVMC22/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 # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 161s ok 5 /context/remove-device-closed 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 161s # libfprint-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-Z2MC22/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-context:2312): libfprint-virtual_image-DEBUG: 00:00:53.529: 46451109: ../libfprint/drivers/virtual-image.c:216 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2312): libfprint-virtual_device_connection-DEBUG: 00:00:53.529: 46451169: ../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-context:2312): libfprint-virtual_image-DEBUG: 00:00:53.630: 46551537: ../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 /context/remove-device-closing 161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 161s # libfprint-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-XVSD22/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-context:2312): libfprint-virtual_image-DEBUG: 00:00:53.731: 46652676: ../libfprint/drivers/virtual-image.c:216 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2312): libfprint-virtual_device_connection-DEBUG: 00:00:53.731: 46652688: ../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-context:2312): libfprint-virtual_image-DEBUG: 00:00:53.831: 46753156: ../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 7 /context/remove-device-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.8+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-SIUK22/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-context:2312): libfprint-virtual_image-DEBUG: 00:00:53.933: 46854453: ../libfprint/drivers/virtual-image.c:216 161s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2312): libfprint-virtual_device_connection-DEBUG: 00:00:53.933: 46854466: ../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-context:2312): libfprint-virtual_image-DEBUG: 00:00:54.033: 46954854: ../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 /context/remove-device-opening 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.8+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-D03312/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-context:2312): libfprint-virtual_image-DEBUG: 00:00:54.134: 47056228: ../libfprint/drivers/virtual-image.c:216 162s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2312): libfprint-virtual_device_connection-DEBUG: 00:00:54.134: 47056261: ../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 # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s # libfprint-image_device-DEBUG: Activating image device 162s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 162s # libfprint-image_device-DEBUG: Image device activation completed 162s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 162s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 162s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s # libfprint-image_device-DEBUG: Deactivating image device 162s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 162s # libfprint-image_device-DEBUG: Image device deactivation completed 162s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 162s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 162s # libfprint-device-DEBUG: Device reported enroll completion 162s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL 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-context:2312): libfprint-virtual_image-DEBUG: 00:00:54.235: 47156998: ../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 /context/remove-device-active 162s # End of context tests 162s PASS: libfprint-2/fp-context.test 162s Running test: libfprint-2/driver-upektc_img-tcs1s.test 162s ** (umockdev-run:2336): DEBUG: 00:00:54.366: umockdev.vala:127: Created udev test bed /tmp/umockdev.Z3B612 162s ** (umockdev-run:2336): DEBUG: 00:00:54.366: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 162s ** (umockdev-run:2336): DEBUG: 00:00:54.370: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 162s ** (umockdev-run:2336): DEBUG: 00:00:54.372: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z3B612/dev/bus/usb/003/004 162s ** (umockdev-run:2336): DEBUG: 00:00:54.372: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 162s ** (umockdev-run:2336): DEBUG: 00:00:54.375: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 162s ** (umockdev-run:2336): DEBUG: 00:00:54.376: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z3B612/dev/bus/usb/003/001 162s ** (umockdev-run:2336): DEBUG: 00:00:54.376: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 162s ** (umockdev-run:2336): DEBUG: 00:00:54.378: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 162s ** (umockdev-run:2336): DEBUG: 00:00:54.379: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1 162s ** (umockdev-run:2336): DEBUG: 00:00:54.380: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 162s (process:2340): libfprint-context-DEBUG: 00:00:54.446: Initializing FpContext (libfprint version 1.94.8+tod1) 162s (process:2340): libfprint-tod-DEBUG: 00:00:54.446: 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 (process:2340): libfprint-context-DEBUG: 00:00:54.448: No driver found for USB device 1D6B:0002 162s (process:2340): libfprint-device-DEBUG: 00:00:54.448: Device reported probe completion 162s (process:2340): libfprint-device-DEBUG: 00:00:54.448: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:2340): libfprint-device-DEBUG: 00:00:54.448: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.449: Image device open completed 162s (process:2340): libfprint-device-DEBUG: 00:00:54.449: Device reported open completion 162s (process:2340): libfprint-device-DEBUG: 00:00:54.449: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:2340): libfprint-device-DEBUG: 00:00:54.449: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2340): libfprint-device-DEBUG: 00:00:54.449: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.450: Activating image device 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.450: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.450: [upektc_img] ACTIVATE_NUM_STATES entering state 0 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.450: [upektc_img] ACTIVATE_NUM_STATES entering state 1 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.451: [upektc_img] ACTIVATE_NUM_STATES entering state 2 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.451: [upektc_img] ACTIVATE_NUM_STATES entering state 3 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.452: [upektc_img] ACTIVATE_NUM_STATES entering state 4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.452: [upektc_img] ACTIVATE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.453: [upektc_img] ACTIVATE_NUM_STATES entering state 6 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.453: [upektc_img] ACTIVATE_NUM_STATES entering state 7 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.454: [upektc_img] ACTIVATE_NUM_STATES entering state 8 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.454: [upektc_img] ACTIVATE_NUM_STATES entering state 9 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.455: [upektc_img] ACTIVATE_NUM_STATES entering state 10 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.455: [upektc_img] ACTIVATE_NUM_STATES entering state 11 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.456: Sensor type : TCS1x, width x height: 256 x 360 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.456: [upektc_img] ACTIVATE_NUM_STATES completed successfully 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.456: Image device activation completed 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.456: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.456: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 162s (process:2340): libfprint-device-DEBUG: 00:00:54.456: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.456: [upektc_img] CAPTURE_NUM_STATES entering state 0 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.456: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.457: request completed, len: 0000 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.457: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.457: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.457: 18th byte is 0c 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.457: [upektc_img] CAPTURE_NUM_STATES entering state 3 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.458: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.458: request completed, len: 0000 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.458: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.458: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.458: 18th byte is 13 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.458: [upektc_img] CAPTURE_NUM_STATES entering state 3 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.459: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.459: request completed, len: 0000 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.459: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.460: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.460: 18th byte is 00 162s (process:2340): libfprint-device-DEBUG: 00:00:54.460: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.460: [upektc_img] CAPTURE_NUM_STATES entering state 3 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.460: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.461: request completed, len: 0000 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.461: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.461: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.461: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.461: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.461: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.461: request completed, len: 07c4 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.461: Image device reported finger status: on 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.461: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.461: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.462: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.462: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.462: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.462: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.462: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.463: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.463: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.463: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.463: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.463: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.463: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.463: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.464: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.464: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.464: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.465: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.465: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.465: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.465: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.465: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.465: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.466: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.466: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.466: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.466: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.466: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.466: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.466: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.467: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.467: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.467: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.467: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.467: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.468: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.468: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.468: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.469: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.469: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.469: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.469: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.469: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.469: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.469: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.470: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.470: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.470: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.470: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.470: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.470: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.471: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.471: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.471: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.471: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.471: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.471: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.471: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.472: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.472: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.472: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.472: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.472: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.472: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.472: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.473: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.473: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.473: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.473: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.473: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.474: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.474: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.474: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.475: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.475: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.475: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.475: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.475: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.475: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.475: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.476: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.476: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.476: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.476: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.476: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.476: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.477: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.477: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.477: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.477: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.477: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.477: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.477: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.478: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.478: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.478: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.478: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.478: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.479: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.479: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.479: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.479: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.479: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.479: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.479: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.480: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.480: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.480: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.480: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.480: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.480: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.480: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.481: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.481: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.481: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.482: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.482: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.482: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.482: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.482: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.482: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.482: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.483: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.483: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.483: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.483: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.483: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.483: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.484: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.484: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.484: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.484: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.484: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.484: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.484: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.485: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.485: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.485: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.485: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.485: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.485: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.485: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.486: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.486: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.486: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.486: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.486: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.486: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.486: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.487: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.487: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.487: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.487: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.487: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.487: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.487: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.487: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.488: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.488: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.488: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.488: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.488: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.488: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.488: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.489: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.489: response_size is 2052, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.489: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.489: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.489: request completed, len: 07c4 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.489: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.489: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.490: request completed, len: 0040 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.490: response_size is 814, actual_length is 64 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.490: Waiting for rest of transfer 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.490: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.490: request completed, len: 02ee 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.490: Image size is 51840 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.490: Image device captured an image 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.490: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 162s (process:2340): libfprint-device-DEBUG: 00:00:54.490: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2340): libfprint-device-DEBUG: 00:00:54.490: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.490: Image device reported finger status: off 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.490: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.490: Deactivating image device 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.490: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.490: [upektc_img] CAPTURE_NUM_STATES completed successfully 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.490: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.498: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 162s (process:2340): libfprint-SSM-DEBUG: 00:00:54.499: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 162s (process:2340): libfprint-upektc_img-DEBUG: 00:00:54.499: Deactivate completed 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.499: Image device deactivation completed 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.499: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 162s (process:2340): libfprint-image-DEBUG: 00:00:54.510: Minutiae scan completed in 0.019810 secs 162s (process:2340): libfprint-device-DEBUG: 00:00:54.510: Device reported capture completion 162s (process:2340): libfprint-device-DEBUG: 00:00:54.510: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 162s (process:2340): libfprint-device-DEBUG: 00:00:54.510: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 162s (process:2340): libfprint-image_device-DEBUG: 00:00:54.510: Image device close completed 162s (process:2340): libfprint-device-DEBUG: 00:00:54.510: Device reported close completion 162s (process:2340): libfprint-device-DEBUG: 00:00:54.510: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 162s (process:2340): libfprint-device-DEBUG: 00:00:54.510: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 162s ** (umockdev-run:2336): DEBUG: 00:00:54.592: umockdev.vala:154: Removing test bed /tmp/umockdev.Z3B612 162s (umockdev-run:2336): GLib-DEBUG: 00:00:54.595: unsetenv() is not thread-safe and should not be used after threads are created 162s Comparing PNGs /tmp/libfprint-umockdev-test-_lfwweb6/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 162s PASS: libfprint-2/driver-upektc_img-tcs1s.test 162s Running test: libfprint-2/driver-realtek.test 162s ** (umockdev-run:2349): DEBUG: 00:00:54.642: umockdev.vala:127: Created udev test bed /tmp/umockdev.MZ6B22 162s ** (umockdev-run:2349): DEBUG: 00:00:54.642: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-8 162s ** (umockdev-run:2349): DEBUG: 00:00:54.644: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-8 (subsystem usb) 162s ** (umockdev-run:2349): DEBUG: 00:00:54.645: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.MZ6B22/dev/bus/usb/001/025 162s ** (umockdev-run:2349): DEBUG: 00:00:54.645: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 162s ** (umockdev-run:2349): DEBUG: 00:00:54.646: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 162s ** (umockdev-run:2349): DEBUG: 00:00:54.647: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.MZ6B22/dev/bus/usb/001/001 162s ** (umockdev-run:2349): DEBUG: 00:00:54.647: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 162s ** (umockdev-run:2349): DEBUG: 00:00:54.647: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 162s (process:2353): libfprint-context-DEBUG: 00:00:54.704: Initializing FpContext (libfprint version 1.94.8+tod1) 162s (process:2353): libfprint-tod-DEBUG: 00:00:54.705: 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 (process:2353): libfprint-context-DEBUG: 00:00:54.706: No driver found for USB device 1D6B:0002 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.706: 47627636: ../libfprint/drivers/realtek/realtek.c:1225 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.707: Device name: Realtek USB2.0 Finger Print Bridge 162s (process:2353): libfprint-device-DEBUG: 00:00:54.707: Device reported probe completion 162s (process:2353): libfprint-device-DEBUG: 00:00:54.707: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.707: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.708: 47629949: ../libfprint/drivers/realtek/realtek.c:1270 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.708: [realtek] Init entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.709: [realtek] Init entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.709: [realtek] Init entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.709: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.710: [realtek] Init completed successfully 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.710: Init complete! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.710: Device reported open completion 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.710: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-device-DEBUG: 00:00:54.710: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.710: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.710: 47631868: ../libfprint/drivers/realtek/realtek.c:1333 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.710: Successfully cleared storage 162s (process:2353): libfprint-device-DEBUG: 00:00:54.710: Device reported deletion completion 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.711: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-device-DEBUG: 00:00:54.711: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.711: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.711: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.711: 47632855: ../libfprint/drivers/realtek/realtek.c:1202 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.711: [realtek] Enroll entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] Enroll entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.713: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.713: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.713: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.713: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.714: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.714: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-device-DEBUG: 00:00:54.714: Device reported enroll progress, reported 1 of 8 have been completed 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.714: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.714: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.714: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.715: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.716: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-device-DEBUG: 00:00:54.716: Device reported enroll progress, reported 2 of 8 have been completed 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.716: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.716: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.716: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.717: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.717: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.717: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.717: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.718: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-device-DEBUG: 00:00:54.718: Device reported enroll progress, reported 3 of 8 have been completed 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.718: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.718: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.718: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.718: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.719: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.719: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.719: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.719: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.720: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-device-DEBUG: 00:00:54.720: Device reported enroll progress, reported 4 of 8 have been completed 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.720: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.720: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.720: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.721: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.721: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.721: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.721: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.722: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-device-DEBUG: 00:00:54.722: Device reported enroll progress, reported 5 of 8 have been completed 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.722: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.723: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.723: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.723: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.724: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-device-DEBUG: 00:00:54.724: Device reported enroll progress, reported 6 of 8 have been completed 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.724: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.725: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.725: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.725: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.726: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-device-DEBUG: 00:00:54.726: Device reported enroll progress, reported 7 of 8 have been completed 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.727: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.727: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.727: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.728: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-device-DEBUG: 00:00:54.728: Device reported enroll progress, reported 8 of 8 have been completed 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.728: [realtek] Enroll entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.728: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.728: [realtek] Enroll entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.728: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.729: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.729: [realtek] Enroll entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.729: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.730: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.730: [realtek] Enroll entering state 5 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.730: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.730: [realtek] Enroll entering state 6 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.730: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.731: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.731: [realtek] Enroll completed successfully 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.731: Enrollment complete! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.731: Device reported enroll completion 162s (process:2353): libfprint-device-DEBUG: 00:00:54.731: Print for finger FP_FINGER_UNKNOWN enrolled 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.731: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-device-DEBUG: 00:00:54.731: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.731: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.731: 47653120: ../libfprint/drivers/realtek/realtek.c:1345 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.732: Query templates complete! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.732: Device reported listing completion 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.732: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-device-DEBUG: 00:00:54.732: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.732: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.732: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.732: 47653930: ../libfprint/drivers/realtek/realtek.c:1178 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.732: [realtek] Verify & Identify entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] Verify & Identify entering state 1 162s (process:2353): libfprint-device-DEBUG: 00:00:54.733: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] Verify & Identify entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.734: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.734: [realtek] Verify & Identify entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.734: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.734: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.734: [realtek] Verify & Identify entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.735: Device reported verify result 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] Verify & Identify entering state 5 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] Verify & Identify completed successfully 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.735: Verify complete! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.735: Device reported verify completion 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.735: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-device-DEBUG: 00:00:54.735: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.735: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.736: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.736: 47657571: ../libfprint/drivers/realtek/realtek.c:1178 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.736: [realtek] Verify & Identify entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.736: [realtek] Verify & Identify entering state 1 162s (process:2353): libfprint-device-DEBUG: 00:00:54.736: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.737: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.737: [realtek] Verify & Identify entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.737: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.738: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.738: [realtek] Verify & Identify entering state 3 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.738: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.738: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.738: [realtek] Verify & Identify entering state 4 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.738: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-device-DEBUG: 00:00:54.739: Device reported identify result 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.739: [realtek] Verify & Identify completed successfully 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.739: Verify complete! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.739: Device reported identify completion 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.739: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-device-DEBUG: 00:00:54.739: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.739: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.739: 47661101: ../libfprint/drivers/realtek/realtek.c:1314 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.739: [realtek] Delete print entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.740: [realtek] Delete print entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.740: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.740: [realtek] Delete print completed successfully 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.740: Delete print complete! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.740: Device reported deletion completion 162s (process:2353): libfprint-SSM-DEBUG: 00:00:54.740: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:2353): libfprint-device-DEBUG: 00:00:54.740: Completing action FPI_DEVICE_ACTION_DELETE in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.740: Not updating temperature model, device can run continuously! 162s (process:2353): libfprint-realtek-DEBUG: 00:00:54.740: 47662368: ../libfprint/drivers/realtek/realtek.c:1302 162s (process:2353): libfprint-device-DEBUG: 00:00:54.741: Device reported close completion 162s (process:2353): libfprint-device-DEBUG: 00:00:54.741: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 162s (process:2353): libfprint-device-DEBUG: 00:00:54.741: Not updating temperature model, device can run continuously! 162s enrolling 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9800a200 (FpiDeviceRealtek at 0x2d70020)>, 1, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9800a200 (FpiDeviceRealtek at 0x2d70020)>, 2, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9800a200 (FpiDeviceRealtek at 0x2d70020)>, 3, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9800a200 (FpiDeviceRealtek at 0x2d70020)>, 4, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9800a200 (FpiDeviceRealtek at 0x2d70020)>, 5, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9800a200 (FpiDeviceRealtek at 0x2d70020)>, 6, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9800a200 (FpiDeviceRealtek at 0x2d70020)>, 7, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9800a200 (FpiDeviceRealtek at 0x2d70020)>, 8, None, None, None) 162s enroll done 162s listing 162s listing done 162s verifying 162s verify done 162s async identifying 162s indentification_done: 162s deleting 162s delete done 162s ** (umockdev-run:2349): DEBUG: 00:00:54.752: umockdev.vala:154: Removing test bed /tmp/umockdev.MZ6B22 162s (umockdev-run:2349): GLib-DEBUG: 00:00:54.754: unsetenv() is not thread-safe and should not be used after threads are created 162s PASS: libfprint-2/driver-realtek.test 162s Running test: libfprint-2/driver-upektc_img.test 162s ** (umockdev-run:2361): DEBUG: 00:00:54.785: umockdev.vala:127: Created udev test bed /tmp/umockdev.WLVE22 162s ** (umockdev-run:2361): DEBUG: 00:00:54.785: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 162s ** (umockdev-run:2361): DEBUG: 00:00:54.786: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 162s ** (umockdev-run:2361): DEBUG: 00:00:54.788: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WLVE22/dev/bus/usb/001/003 162s ** (umockdev-run:2361): DEBUG: 00:00:54.788: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 162s ** (umockdev-run:2361): DEBUG: 00:00:54.789: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 162s ** (umockdev-run:2361): DEBUG: 00:00:54.790: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WLVE22/dev/bus/usb/001/002 162s ** (umockdev-run:2361): DEBUG: 00:00:54.790: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 162s ** (umockdev-run:2361): DEBUG: 00:00:54.791: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 162s ** (umockdev-run:2361): DEBUG: 00:00:54.792: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WLVE22/dev/bus/usb/001/001 162s ** (umockdev-run:2361): DEBUG: 00:00:54.792: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0 162s ** (umockdev-run:2361): DEBUG: 00:00:54.792: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 162s (process:2365): libfprint-context-DEBUG: 00:00:54.853: Initializing FpContext (libfprint version 1.94.8+tod1) 162s (process:2365): libfprint-tod-DEBUG: 00:00:54.853: 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 (process:2365): libfprint-context-DEBUG: 00:00:54.854: No driver found for USB device 8087:0020 162s (process:2365): libfprint-context-DEBUG: 00:00:54.854: No driver found for USB device 1D6B:0002 162s (process:2365): libfprint-device-DEBUG: 00:00:54.854: Device reported probe completion 162s (process:2365): libfprint-device-DEBUG: 00:00:54.854: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:2365): libfprint-device-DEBUG: 00:00:54.854: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.855: Image device open completed 162s (process:2365): libfprint-device-DEBUG: 00:00:54.855: Device reported open completion 162s (process:2365): libfprint-device-DEBUG: 00:00:54.855: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:2365): libfprint-device-DEBUG: 00:00:54.855: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2365): libfprint-device-DEBUG: 00:00:54.855: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.855: Activating image device 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.856: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.856: [upektc_img] ACTIVATE_NUM_STATES entering state 0 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.856: [upektc_img] ACTIVATE_NUM_STATES entering state 1 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.856: [upektc_img] ACTIVATE_NUM_STATES entering state 2 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.856: [upektc_img] ACTIVATE_NUM_STATES entering state 3 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.857: [upektc_img] ACTIVATE_NUM_STATES entering state 4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.857: [upektc_img] ACTIVATE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.857: [upektc_img] ACTIVATE_NUM_STATES entering state 6 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.857: [upektc_img] ACTIVATE_NUM_STATES entering state 7 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.858: [upektc_img] ACTIVATE_NUM_STATES entering state 8 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.858: [upektc_img] ACTIVATE_NUM_STATES entering state 9 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.858: [upektc_img] ACTIVATE_NUM_STATES entering state 10 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.858: [upektc_img] ACTIVATE_NUM_STATES entering state 11 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.859: Sensor type : TCS4x, width x height: 192 x 512 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.859: [upektc_img] ACTIVATE_NUM_STATES completed successfully 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.859: Image device activation completed 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.859: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.859: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 162s (process:2365): libfprint-device-DEBUG: 00:00:54.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.859: [upektc_img] CAPTURE_NUM_STATES entering state 0 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.859: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.859: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.859: 18th byte is 0c 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.859: [upektc_img] CAPTURE_NUM_STATES entering state 3 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.859: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.860: request completed, len: 0040 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.860: [upektc_img] CAPTURE_NUM_STATES entering state 4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.860: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.860: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.860: 18th byte is 00 162s (process:2365): libfprint-device-DEBUG: 00:00:54.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.860: [upektc_img] CAPTURE_NUM_STATES entering state 3 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.860: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.861: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.861: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.861: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.861: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.861: request completed, len: 07c4 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.861: Image device reported finger status: on 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.861: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.861: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.861: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.862: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.862: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.862: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.862: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.862: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.862: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.863: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.863: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.863: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.863: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.863: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.863: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.863: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.864: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.864: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.864: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.864: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.864: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.864: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.864: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.864: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.865: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.865: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.865: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.865: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.865: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.865: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.865: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.865: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.865: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.865: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.865: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.866: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.866: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.866: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.866: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.866: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.866: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.866: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.866: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.866: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.867: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.867: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.867: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.867: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.867: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.867: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.867: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.868: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.868: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.868: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.868: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.868: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.868: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.868: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.868: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.869: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.869: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.869: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.869: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.869: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.869: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.869: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.870: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.870: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.870: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.870: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.870: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.870: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.870: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.870: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.870: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.870: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.870: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.871: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.871: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.871: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.871: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.871: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.871: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.871: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.871: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.871: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.872: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.872: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.872: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.872: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.872: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.872: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.872: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.872: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.873: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.873: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.873: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.873: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.873: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.873: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.873: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.873: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.873: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.873: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.873: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.874: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.874: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.874: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.874: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.874: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.874: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.874: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.874: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.874: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.875: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.875: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.875: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.875: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.875: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.875: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.875: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.875: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.876: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.876: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.876: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.876: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.876: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.876: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.876: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.876: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.876: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.876: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.876: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.877: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.877: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.877: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.877: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.877: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.877: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.877: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.877: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.877: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.878: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.878: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.878: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.878: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.878: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.878: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.878: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.878: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.879: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.879: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.879: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.879: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.879: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.879: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.879: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.879: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.879: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.879: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.879: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.880: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.880: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.880: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.880: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.880: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.880: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.880: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.880: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.880: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.881: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.881: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.881: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.881: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.881: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.881: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.881: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.881: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.881: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.881: response_size is 2052, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.881: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.881: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.882: request completed, len: 07c4 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.882: [upektc_img] CAPTURE_NUM_STATES entering state 5 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.882: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.882: request completed, len: 0040 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.882: response_size is 186, actual_length is 64 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.882: Waiting for rest of transfer 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.882: [upektc_img] CAPTURE_NUM_STATES entering state 1 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.882: request completed, len: 007a 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.882: Image size is 55296 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.882: Image device captured an image 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.883: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 162s (process:2365): libfprint-device-DEBUG: 00:00:54.883: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:2365): libfprint-device-DEBUG: 00:00:54.888: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.888: Image device reported finger status: off 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.888: Deactivating image device 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.888: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.888: [upektc_img] CAPTURE_NUM_STATES completed successfully 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.888: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.888: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 162s (process:2365): libfprint-SSM-DEBUG: 00:00:54.889: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 162s (process:2365): libfprint-upektc_img-DEBUG: 00:00:54.889: Deactivate completed 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.889: Image device deactivation completed 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.889: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 162s (process:2365): libfprint-image-DEBUG: 00:00:54.894: Minutiae scan completed in 0.011360 secs 162s (process:2365): libfprint-device-DEBUG: 00:00:54.894: Device reported capture completion 162s (process:2365): libfprint-device-DEBUG: 00:00:54.894: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 162s (process:2365): libfprint-device-DEBUG: 00:00:54.894: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 162s (process:2365): libfprint-image_device-DEBUG: 00:00:54.894: Image device close completed 162s (process:2365): libfprint-device-DEBUG: 00:00:54.894: Device reported close completion 162s (process:2365): libfprint-device-DEBUG: 00:00:54.894: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 162s (process:2365): libfprint-device-DEBUG: 00:00:54.894: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s ** (umockdev-run:2361): DEBUG: 00:00:54.974: umockdev.vala:154: Removing test bed /tmp/umockdev.WLVE22 163s (umockdev-run:2361): GLib-DEBUG: 00:00:54.977: unsetenv() is not thread-safe and should not be used after threads are created 163s Comparing PNGs /tmp/libfprint-umockdev-test-z9_wo_qf/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 163s PASS: libfprint-2/driver-upektc_img.test 163s Running test: libfprint-2/driver-egismoc.test 163s ** (umockdev-run:2374): DEBUG: 00:00:55.025: umockdev.vala:127: Created udev test bed /tmp/umockdev.I7H112 163s ** (umockdev-run:2374): DEBUG: 00:00:55.025: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 163s ** (umockdev-run:2374): DEBUG: 00:00:55.026: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 163s ** (umockdev-run:2374): DEBUG: 00:00:55.028: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.I7H112/dev/bus/usb/003/012 163s ** (umockdev-run:2374): DEBUG: 00:00:55.028: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 163s ** (umockdev-run:2374): DEBUG: 00:00:55.029: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 163s ** (umockdev-run:2374): DEBUG: 00:00:55.030: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.I7H112/dev/bus/usb/003/001 163s ** (umockdev-run:2374): DEBUG: 00:00:55.030: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 163s ** (umockdev-run:2374): DEBUG: 00:00:55.030: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 163s (process:2378): libfprint-context-DEBUG: 00:00:55.087: Initializing FpContext (libfprint version 1.94.8+tod1) 163s (process:2378): libfprint-tod-DEBUG: 00:00:55.087: 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 (process:2378): libfprint-egismoc-DEBUG: 00:00:55.088: 48009668: ../libfprint/drivers/egismoc/egismoc.c:1597 163s (process:2378): libfprint-context-DEBUG: 00:00:55.088: No driver found for USB device 1D6B:0002 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.088: egismoc_probe enter --> 163s (process:2378): libfprint-device-DEBUG: 00:00:55.089: Device reported probe completion 163s (process:2378): libfprint-device-DEBUG: 00:00:55.089: Completing action FPI_DEVICE_ACTION_PROBE in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.089: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.089: Opening device 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.089: [egismoc] DEV_INIT_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.090: [egismoc] DEV_INIT_STATES entering state 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.090: [egismoc] DEV_INIT_STATES entering state 2 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.090: [egismoc] DEV_INIT_STATES entering state 3 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.091: [egismoc] DEV_INIT_STATES entering state 4 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.091: [egismoc] DEV_INIT_STATES entering state 5 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.091: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.091: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.091: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.091: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.091: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.091: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.091: Firmware version callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.091: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.091: Device firmware version is 9050.1.1.81 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.091: [egismoc] DEV_INIT_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.091: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.091: Device reported open completion 163s (process:2378): libfprint-device-DEBUG: 00:00:55.091: Completing action FPI_DEVICE_ACTION_OPEN in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.091: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: List 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.092: [egismoc] LIST_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.092: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.092: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.092: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Device fingerprint 3: FP1-20231016-3-5159A026-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Device fingerprint 4: FP1-20231016-4-A25C1212-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Number of currently enrolled fingerprints on the device is 7 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.092: [egismoc] LIST_STATES entering state 1 163s (process:2378): libfprint-device-DEBUG: 00:00:55.092: Device reported listing completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.092: [egismoc] LIST_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.092: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.092: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.092: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Clear storage 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.093: [egismoc] DELETE_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.093: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.093: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.093: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Device fingerprint 3: FP1-20231016-3-5159A026-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Device fingerprint 4: FP1-20231016-4-A25C1212-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Number of currently enrolled fingerprints on the device is 7 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.093: [egismoc] DELETE_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Get delete command 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.093: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.093: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.094: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.094: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.094: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.094: Delete callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.094: Response prefix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.094: Device reported deletion completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.094: [egismoc] DELETE_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.094: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.094: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.094: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.094: List 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.094: [egismoc] LIST_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.094: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.094: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.094: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.094: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.094: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.094: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: Number of currently enrolled fingerprints on the device is 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.095: [egismoc] LIST_STATES entering state 1 163s (process:2378): libfprint-device-DEBUG: 00:00:55.095: Device reported listing completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.095: [egismoc] LIST_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.095: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.095: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2378): libfprint-device-DEBUG: 00:00:55.095: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: Enroll 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.095: [egismoc] ENROLL_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.095: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.095: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.095: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.095: Number of currently enrolled fingerprints on the device is 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.096: [egismoc] ENROLL_STATES entering state 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.096: [egismoc] ENROLL_STATES entering state 2 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.096: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.096: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.096: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.096: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.096: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.096: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.096: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.096: [egismoc] ENROLL_STATES entering state 3 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.096: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.096: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.096: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.097: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.097: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.097: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.097: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.097: [egismoc] ENROLL_STATES entering state 4 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.097: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.097: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.097: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.097: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.097: [egismoc] ENROLL_STATES entering state 5 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.097: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.097: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.097: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.097: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.098: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.098: [egismoc] ENROLL_STATES entering state 6 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Get check command 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.098: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.098: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.098: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Enroll check callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Response suffix valid: yes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.098: [egismoc] ENROLL_STATES entering state 7 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.098: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.098: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.099: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.099: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.099: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.099: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.099: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.099: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.099: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.099: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.099: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.100: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.100: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.100: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.100: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.100: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.100: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.100: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.100: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.100: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.100: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.100: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.100: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.100: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.100: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.100: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.100: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.101: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.101: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.101: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Partial capture successful. Please touch the sensor again (1/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.101: Device reported enroll progress, reported 1 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.101: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.101: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.101: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.101: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.102: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.102: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.102: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.102: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.102: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.102: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.102: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.102: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.102: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.102: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.102: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.102: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.102: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.102: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.103: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.103: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.103: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.103: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.103: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Partial capture successful. Please touch the sensor again (2/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.103: Device reported enroll progress, reported 2 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.103: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.103: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.103: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.103: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.104: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.104: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.104: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.104: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.104: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.104: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.104: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.104: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.104: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.104: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.104: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.104: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.104: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.105: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.105: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.105: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.105: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.105: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.105: Device reported enroll progress, reported 2 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.105: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.105: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.105: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.105: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.106: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.106: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.106: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.106: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.106: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.106: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.106: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.106: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.106: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.106: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.106: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.106: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.106: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.106: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.107: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.107: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.107: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.107: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.107: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Partial capture successful. Please touch the sensor again (3/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.107: Device reported enroll progress, reported 3 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.107: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.107: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.107: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.107: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.108: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.108: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.108: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.108: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.108: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.108: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.108: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.108: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.108: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.108: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.108: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.109: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.109: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Partial capture successful. Please touch the sensor again (4/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.109: Device reported enroll progress, reported 4 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.109: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.109: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.109: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.109: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.109: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.109: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.109: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.110: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.110: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.110: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.110: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.110: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.110: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.110: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.110: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.110: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.110: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.110: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.110: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.110: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.111: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.111: Device reported enroll progress, reported 4 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.111: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.111: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.111: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.111: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.111: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.111: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.111: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.112: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.112: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.112: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.112: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.112: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.112: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.112: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.112: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.112: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.112: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.112: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.112: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.112: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.113: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Partial capture successful. Please touch the sensor again (5/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.113: Device reported enroll progress, reported 5 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.113: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.113: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.113: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.113: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.113: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.113: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.113: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.113: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.114: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.114: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.114: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.114: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.114: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.114: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.114: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Partial capture successful. Please touch the sensor again (6/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.114: Device reported enroll progress, reported 6 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.114: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.114: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.114: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.115: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.115: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.115: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.115: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.115: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.115: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.115: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.115: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.115: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.115: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.115: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.115: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.115: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.115: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.116: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.116: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.116: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.116: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.116: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.116: Device reported enroll progress, reported 6 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.116: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.116: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.116: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.116: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.117: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.117: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.117: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.117: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.117: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.117: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.117: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.117: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.117: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.117: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.117: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.117: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.117: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.118: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.118: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.118: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.118: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.118: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.118: Device reported enroll progress, reported 6 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.118: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.118: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.118: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.118: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.119: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.119: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.119: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.119: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.119: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.119: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.119: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.119: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.119: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.119: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.119: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.120: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.120: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Partial capture successful. Please touch the sensor again (7/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.120: Device reported enroll progress, reported 7 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.120: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.120: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.120: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.120: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.120: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.120: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.120: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.121: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.121: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.121: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.121: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.121: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.121: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.121: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.121: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.121: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.121: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.121: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.121: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.121: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.122: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Partial capture successful. Please touch the sensor again (8/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.122: Device reported enroll progress, reported 8 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.122: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.122: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.122: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.122: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.122: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.122: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.122: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.123: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.123: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.123: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.123: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.123: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.123: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.123: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.123: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.123: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.123: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.123: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.123: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.123: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.123: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.124: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Partial capture successful. Please touch the sensor again (9/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.124: Device reported enroll progress, reported 9 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.124: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.124: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.124: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.124: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.124: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.124: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.124: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.124: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.125: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.125: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.125: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.125: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.125: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.125: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.125: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.125: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.125: Device reported enroll progress, reported 9 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.125: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.125: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.125: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.126: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.126: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.126: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.126: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.126: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.126: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.126: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.126: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.126: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.126: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.126: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.126: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.126: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.126: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.126: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.127: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.127: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.127: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.127: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.127: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Partial capture successful. Please touch the sensor again (10/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.127: Device reported enroll progress, reported 10 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.127: [egismoc] ENROLL_STATES entering state 12 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.127: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.127: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.128: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.128: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.128: [egismoc] ENROLL_STATES entering state 13 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: New fingerprint ID: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.128: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.128: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.128: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.128: [egismoc] ENROLL_STATES entering state 14 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.128: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.128: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] ENROLL_STATES entering state 15 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Enrollment was successful! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Device reported enroll completion 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Print for finger FP_FINGER_LEFT_INDEX enrolled 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] ENROLL_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: List 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] LIST_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Device fingerprint 1: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Number of currently enrolled fingerprints on the device is 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] LIST_STATES entering state 1 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Device reported listing completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] LIST_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-device-DEBUG: 00:00:55.129: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Identify or Verify 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] IDENTIFY_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.129: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.129: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.130: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.130: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.130: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.130: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.130: Device fingerprint 1: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.130: Number of currently enrolled fingerprints on the device is 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.130: [egismoc] IDENTIFY_STATES entering state 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.130: [egismoc] IDENTIFY_STATES entering state 2 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.130: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.130: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.130: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.130: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.131: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.131: [egismoc] IDENTIFY_STATES entering state 3 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.131: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.131: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.131: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.131: [egismoc] IDENTIFY_STATES entering state 4 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.131: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.131: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.131: [egismoc] IDENTIFY_STATES entering state 5 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.131: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.131: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.132: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.132: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.132: [egismoc] IDENTIFY_STATES entering state 6 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Get check command 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.132: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.132: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.132: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Identify check callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Identify successful for: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Verifying against: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-device-DEBUG: 00:00:55.132: Device reported verify result 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.132: [egismoc] IDENTIFY_STATES entering state 7 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.132: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.132: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.133: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.133: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.133: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.133: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.133: [egismoc] IDENTIFY_STATES entering state 8 163s (process:2378): libfprint-device-DEBUG: 00:00:55.133: Device reported verify completion 163s (process:2378): libfprint-device-DEBUG: 00:00:55.133: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.133: [egismoc] IDENTIFY_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.133: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.133: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.133: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-device-DEBUG: 00:00:55.134: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: Identify or Verify 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.134: [egismoc] IDENTIFY_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.134: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.134: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.134: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: Device fingerprint 1: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: Number of currently enrolled fingerprints on the device is 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.134: [egismoc] IDENTIFY_STATES entering state 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.134: [egismoc] IDENTIFY_STATES entering state 2 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.134: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.134: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.134: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.135: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.135: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.135: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.135: [egismoc] IDENTIFY_STATES entering state 3 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.135: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.135: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.135: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.135: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.135: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.135: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.136: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.136: [egismoc] IDENTIFY_STATES entering state 4 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.136: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.136: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.136: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.136: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.136: [egismoc] IDENTIFY_STATES entering state 5 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.136: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.136: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.136: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.136: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.137: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.137: [egismoc] IDENTIFY_STATES entering state 6 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Get check command 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.137: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.137: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.137: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Identify check callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Identify successful for: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-device-DEBUG: 00:00:55.137: Device reported identify result 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.137: [egismoc] IDENTIFY_STATES entering state 7 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.137: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.137: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.137: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.138: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.138: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.138: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.138: [egismoc] IDENTIFY_STATES entering state 8 163s (process:2378): libfprint-device-DEBUG: 00:00:55.138: Device reported identify completion 163s (process:2378): libfprint-device-DEBUG: 00:00:55.138: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.138: [egismoc] IDENTIFY_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.138: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.138: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.138: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-device-DEBUG: 00:00:55.138: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.138: Enroll 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.138: [egismoc] ENROLL_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.138: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.138: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.138: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.138: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.139: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Device fingerprint 1: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Number of currently enrolled fingerprints on the device is 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.139: [egismoc] ENROLL_STATES entering state 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.139: [egismoc] ENROLL_STATES entering state 2 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.139: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.139: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.139: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.139: [egismoc] ENROLL_STATES entering state 3 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.139: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.139: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.140: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.140: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.140: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.140: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.140: [egismoc] ENROLL_STATES entering state 4 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.140: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.140: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.140: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.140: [egismoc] ENROLL_STATES entering state 5 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.140: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.140: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.140: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.140: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] ENROLL_STATES entering state 6 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Get check command 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Enroll check callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Response suffix valid: NO 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.141: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 163s (process:2378): libfprint-device-DEBUG: 00:00:55.141: Device reported enroll completion 163s (process:2378): libfprint-device-DEBUG: 00:00:55.141: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2378): libfprint-device-DEBUG: 00:00:55.141: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.141: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: List 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] LIST_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.141: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.141: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.142: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.142: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.142: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.142: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.142: Device fingerprint 1: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.142: Number of currently enrolled fingerprints on the device is 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.142: [egismoc] LIST_STATES entering state 1 163s (process:2378): libfprint-device-DEBUG: 00:00:55.142: Device reported listing completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.142: [egismoc] LIST_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.142: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.142: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.142: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-device-DEBUG: 00:00:55.142: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.142: Enroll 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.142: [egismoc] ENROLL_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.142: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.142: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.142: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.142: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Device fingerprint 1: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Number of currently enrolled fingerprints on the device is 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] ENROLL_STATES entering state 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] ENROLL_STATES entering state 2 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] ENROLL_STATES entering state 3 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.143: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.143: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.144: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.144: [egismoc] ENROLL_STATES entering state 4 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.144: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.144: [egismoc] ENROLL_STATES entering state 5 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.144: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.144: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.144: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.144: [egismoc] ENROLL_STATES entering state 6 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Get check command 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.144: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.144: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.145: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.145: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Enroll check callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Response suffix valid: yes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.145: [egismoc] ENROLL_STATES entering state 7 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.145: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.145: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.145: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.145: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.145: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.145: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.146: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.146: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.146: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.146: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.146: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.146: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.146: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.146: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.146: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.146: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.146: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.146: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.146: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.146: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.147: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.147: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.147: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.147: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.147: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Partial capture successful. Please touch the sensor again (1/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.147: Device reported enroll progress, reported 1 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.147: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.147: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.147: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.148: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.148: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.148: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.148: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.148: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.148: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.148: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.148: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.148: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.148: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.148: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.148: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.148: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.148: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.149: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.149: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.149: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.149: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.149: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.149: Device reported enroll progress, reported 1 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.149: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.149: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.149: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.149: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.150: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.150: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.150: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.150: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.150: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.150: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.150: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.150: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.150: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.150: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.150: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.151: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.151: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Partial capture successful. Please touch the sensor again (2/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.151: Device reported enroll progress, reported 2 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.151: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.151: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.151: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.151: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.151: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.151: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.151: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.152: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.152: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.152: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.152: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.152: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.152: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.152: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.152: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.152: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.152: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.152: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.152: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.152: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.153: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Partial capture successful. Please touch the sensor again (3/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.153: Device reported enroll progress, reported 3 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.153: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.153: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.153: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.153: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.153: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.153: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.153: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.153: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.154: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.154: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.154: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.154: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.154: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.154: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.154: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.154: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.154: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.154: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.154: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.154: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.154: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.155: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.155: Device reported enroll progress, reported 3 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.155: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.155: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.155: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.155: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.155: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.155: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.155: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.155: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.156: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.156: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.156: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.156: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.156: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.156: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.156: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.156: Device reported enroll progress, reported 3 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.156: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.156: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.156: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.157: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.157: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.157: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.157: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.157: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.157: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.157: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.157: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.157: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.157: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.157: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.157: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.157: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.157: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.158: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.158: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.158: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.158: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.158: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Partial capture successful. Please touch the sensor again (4/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.158: Device reported enroll progress, reported 4 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.158: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.158: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.158: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.158: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.159: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.159: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.159: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.159: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.159: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.159: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.159: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.159: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.159: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.159: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.159: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.159: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.159: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.160: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.160: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.160: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.160: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.160: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Partial capture successful. Please touch the sensor again (5/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.160: Device reported enroll progress, reported 5 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.160: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.160: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.160: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.160: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.161: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.161: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.161: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.161: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.161: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.161: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.161: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.161: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.161: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.161: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.161: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.161: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.161: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.162: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.162: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.162: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.162: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.162: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Partial capture successful. Please touch the sensor again (6/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.162: Device reported enroll progress, reported 6 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.162: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.162: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.162: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.162: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.163: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.163: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.163: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.163: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.163: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.163: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.163: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.163: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.163: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.163: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.164: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.164: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Partial capture successful. Please touch the sensor again (7/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.164: Device reported enroll progress, reported 7 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.164: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.164: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.164: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.164: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.164: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.164: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.164: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.165: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.165: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.165: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.165: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.165: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.165: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.165: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.165: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.165: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.165: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.165: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.165: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.165: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.166: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Partial capture successful. Please touch the sensor again (8/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.166: Device reported enroll progress, reported 8 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.166: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.166: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.166: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.166: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.166: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.166: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.166: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.166: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.167: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.167: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.167: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.167: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.167: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.167: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.167: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Partial capture successful. Please touch the sensor again (9/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.167: Device reported enroll progress, reported 9 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.167: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.167: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.167: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.168: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.168: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.168: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.168: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.168: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.168: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.168: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.168: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.168: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.169: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.169: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.169: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.169: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.169: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.169: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.169: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.169: Device reported enroll progress, reported 9 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.169: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.169: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.169: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.170: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.170: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.170: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.170: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.170: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.170: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.170: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.170: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.170: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.170: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.170: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.170: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.170: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.170: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.171: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.171: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.171: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.171: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.171: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.171: Device reported enroll progress, reported 9 of 10 have been completed 163s listing - device should have prints 163s clear device storage 163s clear done 163s listing - device should be empty 163s enrolling 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 1, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 2, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 3, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 4, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 5, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 6, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 7, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 8, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 9, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 10, , None, None) 163s enroll done 163s listing - device should have 1 print 163s verifying 163s verify done 163s async identifying 163s indentification_done: 163s try to enroll duplicate 163s duplicate enroll attempt done 163s listing - device should still only have 1 print 163s enroll new finger 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 1, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 2, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 3, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 4, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 5, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 6, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 7, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 8, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 9, , None, None) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: (process:2378): libfprint-SSM-DEBUG: 00:00:55.171: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.171: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.171: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.171: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.172: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.172: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.172: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.172: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.172: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.172: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.172: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.172: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.172: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.172: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.172: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.173: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.173: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Response suffix valid: NO 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Response suffix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.173: Device reported enroll progress, reported 9 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.173: [egismoc] ENROLL_STATES entering state 8 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.173: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.173: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.173: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.173: [egismoc] ENROLL_STATES entering state 9 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.173: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.173: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.174: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.174: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.174: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.174: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.174: [egismoc] ENROLL_STATES entering state 10 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.174: Wait for finger on sensor 163s (process:2378): libfprint-device-DEBUG: 00:00:55.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.174: Finger on sensor callback 163s (process:2378): libfprint-device-DEBUG: 00:00:55.174: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.174: [egismoc] ENROLL_STATES entering state 11 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.174: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.174: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.174: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.174: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.175: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Read capture callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Response prefix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Response suffix valid: yes 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Partial capture successful. Please touch the sensor again (10/10) 163s (process:2378): libfprint-device-DEBUG: 00:00:55.175: Device reported enroll progress, reported 10 of 10 have been completed 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.175: [egismoc] ENROLL_STATES entering state 12 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.175: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.175: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.175: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.175: [egismoc] ENROLL_STATES entering state 13 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: New fingerprint ID: FP1-00000000-7-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.175: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.175: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.175: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] ENROLL_STATES entering state 14 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Task SSM next state callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] ENROLL_STATES entering state 15 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Enrollment was successful! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.176: Device reported enroll completion 163s (process:2378): libfprint-device-DEBUG: 00:00:55.176: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:2378): libfprint-device-DEBUG: 00:00:55.176: Print for finger FP_FINGER_RIGHT_INDEX enrolled 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] ENROLL_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.176: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.176: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: List 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] LIST_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.176: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.176: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.177: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Device fingerprint 1: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Device fingerprint 2: FP1-00000000-7-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Number of currently enrolled fingerprints on the device is 2 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.177: [egismoc] LIST_STATES entering state 1 163s (process:2378): libfprint-device-DEBUG: 00:00:55.177: Device reported listing completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.177: [egismoc] LIST_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.177: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.177: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Delete 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.177: [egismoc] DELETE_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.177: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.177: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.177: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Device fingerprint 1: FP1-00000000-2-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Device fingerprint 2: FP1-00000000-7-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Number of currently enrolled fingerprints on the device is 2 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.177: [egismoc] DELETE_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.177: Get delete command 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.178: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.178: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.178: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Delete callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Response prefix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.178: Device reported deletion completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.178: [egismoc] DELETE_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.178: Completing action FPI_DEVICE_ACTION_DELETE in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.178: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: List 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.178: [egismoc] LIST_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.178: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.178: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.178: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Device fingerprint 1: FP1-00000000-7-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Number of currently enrolled fingerprints on the device is 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] LIST_STATES entering state 1 163s (process:2378): libfprint-device-DEBUG: 00:00:55.179: Device reported listing completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] LIST_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.179: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.179: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Clear storage 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] DELETE_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Device fingerprint 1: FP1-00000000-7-00000000-nobody 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Number of currently enrolled fingerprints on the device is 1 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] DELETE_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Get delete command 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.179: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.179: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.180: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Delete callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Response prefix valid: yes 163s (process:2378): libfprint-device-DEBUG: 00:00:55.180: Device reported deletion completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.180: [egismoc] DELETE_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.180: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.180: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: List 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.180: [egismoc] LIST_STATES entering state 0 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Execute command and get response 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Get check bytes 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.180: [egismoc] CMD_STATES entering state 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.180: [egismoc] CMD_STATES entering state 1 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Command receive callback 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.180: [egismoc] CMD_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: List callback 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Number of currently enrolled fingerprints on the device is 0 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.180: [egismoc] LIST_STATES entering state 1 163s (process:2378): libfprint-device-DEBUG: 00:00:55.180: Device reported listing completion 163s (process:2378): libfprint-SSM-DEBUG: 00:00:55.180: [egismoc] LIST_STATES completed successfully 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Task SSM done 163s (process:2378): libfprint-device-DEBUG: 00:00:55.180: Completing action FPI_DEVICE_ACTION_LIST in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.180: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Closing device 163s (process:2378): libfprint-egismoc-DEBUG: 00:00:55.180: Cancel 163s (process:2378): libfprint-device-DEBUG: 00:00:55.180: Device reported close completion 163s (process:2378): libfprint-device-DEBUG: 00:00:55.181: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 163s (process:2378): libfprint-device-DEBUG: 00:00:55.181: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 163s finger status: 163s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffabc0e3c0 (FpiDeviceEgisMoc at 0x28fd8c0)>, 10, , None, None) 163s enroll new finger done 163s listing - device should have 2 prints 163s deleting first print 163s delete done 163s listing - device should only have second print 163s clear device storage 163s clear done 163s listing - device should be empty 163s ** (umockdev-run:2374): DEBUG: 00:00:55.193: umockdev.vala:154: Removing test bed /tmp/umockdev.I7H112 163s (umockdev-run:2374): GLib-DEBUG: 00:00:55.195: unsetenv() is not thread-safe and should not be used after threads are created 163s PASS: libfprint-2/driver-egismoc.test 163s Running test: libfprint-2/fp-device.test 163s TAP version 14 163s # random seed: R02S603f79d97673ab8b057dfab35232abf3 163s 1..17 163s # Start of device tests 163s # Start of async tests 163s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+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-5NS212/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:2384): libfprint-virtual_image-DEBUG: 00:00:55.204: 48126327: ../libfprint/drivers/virtual-image.c:216 163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:55.204: 48126369: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:55.305: 48226748: ../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 1 /device/async/open 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.8+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-7ZN912/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:2384): libfprint-virtual_image-DEBUG: 00:00:55.406: 48327888: ../libfprint/drivers/virtual-image.c:216 163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:55.406: 48327906: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:55.506: 48428286: ../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 2 /device/async/close 163s # End of async tests 163s # Start of sync 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.8+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-O0IB22/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:2384): libfprint-virtual_image-DEBUG: 00:00:55.607: 48529399: ../libfprint/drivers/virtual-image.c:216 163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:55.608: 48529420: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:55.708: 48629751: ../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 3 /device/sync/open 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.8+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-VNKI22/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:2384): libfprint-virtual_image-DEBUG: 00:00:55.809: 48730988: ../libfprint/drivers/virtual-image.c:216 163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:55.809: 48731007: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:55.909: 48831376: ../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 4 /device/sync/close 164s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # 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 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-EZ3012/virtual_image.socket 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:56.011: 48932563: ../libfprint/drivers/virtual-image.c:216 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:56.011: 48932582: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:56.111: 49032936: ../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 5 /device/sync/get_driver 164s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # 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 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FBM212/virtual_image.socket 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:56.212: 49134042: ../libfprint/drivers/virtual-image.c:216 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:56.212: 49134062: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:56.312: 49234397: ../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 6 /device/sync/get_device_id 164s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # 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 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FW6912/virtual_image.socket 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:56.414: 49335843: ../libfprint/drivers/virtual-image.c:216 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:56.414: 49335869: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:56.514: 49436335: ../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 7 /device/sync/get_name 164s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # 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 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-IMCB22/virtual_image.socket 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:56.616: 49537633: ../libfprint/drivers/virtual-image.c:216 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:56.616: 49537660: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:56.716: 49638174: ../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 8 /device/sync/get_scan_type 164s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # 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 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-7JEI22/virtual_image.socket 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:56.818: 49739465: ../libfprint/drivers/virtual-image.c:216 164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:56.818: 49739488: ../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:2384): libfprint-virtual_image-DEBUG: 00:00:56.918: 49839912: ../libfprint/drivers/virtual-image.c:244 165s # libfprint-image_device-DEBUG: Image device close completed 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 165s ok 9 /device/sync/get_finger_status 165s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 165s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 165s # 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 165s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-MJM112/virtual_image.socket 165s # libfprint-context-DEBUG: created 165s # libfprint-device-DEBUG: Device reported probe completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.019: 49941310: ../libfprint/drivers/virtual-image.c:216 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:57.019: 49941330: ../libfprint/drivers/virtual-device-listener.c:153 165s # libfprint-image_device-DEBUG: Image device open completed 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.120: 50041954: ../libfprint/drivers/virtual-image.c:244 165s # libfprint-image_device-DEBUG: Image device close completed 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 165s ok 10 /device/sync/get_nr_enroll_stages 165s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 165s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 165s # 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 165s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-9EW212/virtual_image.socket 165s # libfprint-context-DEBUG: created 165s # libfprint-device-DEBUG: Device reported probe completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.222: 50143457: ../libfprint/drivers/virtual-image.c:216 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:57.222: 50143489: ../libfprint/drivers/virtual-device-listener.c:153 165s # libfprint-image_device-DEBUG: Image device open completed 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.322: 50244073: ../libfprint/drivers/virtual-image.c:244 165s # libfprint-image_device-DEBUG: Image device close completed 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 165s ok 11 /device/sync/supports_identify 165s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 165s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 165s # 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 165s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0U0912/virtual_image.socket 165s # libfprint-context-DEBUG: created 165s # libfprint-device-DEBUG: Device reported probe completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.424: 50345579: ../libfprint/drivers/virtual-image.c:216 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:57.424: 50345599: ../libfprint/drivers/virtual-device-listener.c:153 165s # libfprint-image_device-DEBUG: Image device open completed 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.524: 50446013: ../libfprint/drivers/virtual-image.c:244 165s # libfprint-image_device-DEBUG: Image device close completed 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 165s ok 12 /device/sync/supports_capture 165s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 165s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 165s # 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 165s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FZSB22/virtual_image.socket 165s # libfprint-context-DEBUG: created 165s # libfprint-device-DEBUG: Device reported probe completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.625: 50547253: ../libfprint/drivers/virtual-image.c:216 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:57.625: 50547273: ../libfprint/drivers/virtual-device-listener.c:153 165s # libfprint-image_device-DEBUG: Image device open completed 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.726: 50647873: ../libfprint/drivers/virtual-image.c:244 165s # libfprint-image_device-DEBUG: Image device close completed 165s # libfprint-device-DEBUG: Device reported close completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 165s ok 13 /device/sync/has_storage 165s # Start of open tests 165s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 165s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 165s # 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 165s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2TXI22/virtual_image.socket 165s # libfprint-context-DEBUG: created 165s # libfprint-device-DEBUG: Device reported probe completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.827: 50749316: ../libfprint/drivers/virtual-image.c:216 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:57.827: 50749335: ../libfprint/drivers/virtual-device-listener.c:153 165s # libfprint-image_device-DEBUG: Image device open completed 165s # libfprint-device-DEBUG: Device reported open completion 165s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:57.928: 50849968: ../libfprint/drivers/virtual-image.c:244 166s # libfprint-image_device-DEBUG: Image device close completed 166s # libfprint-device-DEBUG: Device reported close completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 14 /device/sync/open/notify 166s # End of open tests 166s # Start of close tests 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 166s # 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 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-EOK112/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:58.030: 50951439: ../libfprint/drivers/virtual-image.c:216 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:58.030: 50951465: ../libfprint/drivers/virtual-device-listener.c:153 166s Executing: libfprint-2/fp-device.test 166s # libfprint-image_device-DEBUG: Image device open completed 166s # libfprint-device-DEBUG: Device reported open completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:58.130: 51051811: ../libfprint/drivers/virtual-image.c:244 166s # libfprint-image_device-DEBUG: Image device close completed 166s # libfprint-device-DEBUG: Device reported close completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 15 /device/sync/close/notify 166s # End of close tests 166s # Start of identify tests 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 166s # 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 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-43F312/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:58.231: 51153331: ../libfprint/drivers/virtual-image.c:216 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:58.231: 51153370: ../libfprint/drivers/virtual-device-listener.c:153 166s # libfprint-image_device-DEBUG: Image device open completed 166s # libfprint-device-DEBUG: Device reported open completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:58.332: 51253910: ../libfprint/drivers/virtual-image.c:244 166s # libfprint-image_device-DEBUG: Image device close completed 166s # libfprint-device-DEBUG: Device reported close completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 16 /device/sync/identify/cancelled 166s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 166s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 166s # 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 166s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-JMIA22/virtual_image.socket 166s # libfprint-context-DEBUG: created 166s # libfprint-device-DEBUG: Device reported probe completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:58.433: 51355374: ../libfprint/drivers/virtual-image.c:216 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_device_connection-DEBUG: 00:00:58.433: 51355400: ../libfprint/drivers/virtual-device-listener.c:153 166s # libfprint-image_device-DEBUG: Image device open completed 166s # libfprint-device-DEBUG: Device reported open completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2384): libfprint-virtual_image-DEBUG: 00:00:58.534: 51455835: ../libfprint/drivers/virtual-image.c:244 166s # libfprint-image_device-DEBUG: Image device close completed 166s # libfprint-device-DEBUG: Device reported close completion 166s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 166s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 166s ok 17 /device/sync/identify/null-prints 166s # End of identify tests 166s # End of sync tests 166s # End of device tests 166s PASS: libfprint-2/fp-device.test 166s Running test: libfprint-2/driver-egis0570.test 166s ** (umockdev-run:2424): DEBUG: 00:00:58.663: umockdev.vala:127: Created udev test bed /tmp/umockdev.4MFF22 166s ** (umockdev-run:2424): DEBUG: 00:00:58.663: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 166s ** (umockdev-run:2424): DEBUG: 00:00:58.664: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 166s ** (umockdev-run:2424): DEBUG: 00:00:58.665: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4MFF22/dev/bus/usb/001/005 166s ** (umockdev-run:2424): DEBUG: 00:00:58.665: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 166s ** (umockdev-run:2424): DEBUG: 00:00:58.666: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 166s ** (umockdev-run:2424): DEBUG: 00:00:58.667: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4MFF22/dev/bus/usb/001/001 166s ** (umockdev-run:2424): DEBUG: 00:00:58.667: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 166s ** (umockdev-run:2424): DEBUG: 00:00:58.668: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 166s (process:2428): libfprint-context-DEBUG: 00:00:58.729: Initializing FpContext (libfprint version 1.94.8+tod1) 166s (process:2428): libfprint-tod-DEBUG: 00:00:58.729: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 166s (process:2428): libfprint-context-DEBUG: 00:00:58.730: No driver found for USB device 1D6B:0002 166s (process:2428): libfprint-device-DEBUG: 00:00:58.730: Device reported probe completion 166s (process:2428): libfprint-device-DEBUG: 00:00:58.730: Completing action FPI_DEVICE_ACTION_PROBE in idle! 166s (process:2428): libfprint-device-DEBUG: 00:00:58.730: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.731: Image device open completed 166s (process:2428): libfprint-device-DEBUG: 00:00:58.731: Device reported open completion 166s (process:2428): libfprint-device-DEBUG: 00:00:58.731: Completing action FPI_DEVICE_ACTION_OPEN in idle! 166s (process:2428): libfprint-device-DEBUG: 00:00:58.731: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (process:2428): libfprint-device-DEBUG: 00:00:58.731: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.731: Activating image device 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.731: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.731: [egis0570] SM_STATES_NUM entering state 0 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.731: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.731: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.732: Image device activation completed 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.732: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.732: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 166s (process:2428): libfprint-device-DEBUG: 00:00:58.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.732: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.732: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.732: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.733: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.733: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.734: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.734: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.734: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.735: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.735: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.735: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.736: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.736: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.736: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.737: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.737: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.737: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.738: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.738: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.738: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.739: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.739: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.740: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.740: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.740: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.740: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.741: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.741: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.742: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.742: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.742: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.743: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.743: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.743: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.744: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.744: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.744: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.745: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.745: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.745: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.746: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.746: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.747: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.747: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.747: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.747: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.748: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.748: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.748: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.748: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.748: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.748: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.748: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.749: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.749: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.749: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.750: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.750: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.750: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.750: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.750: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.750: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.750: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.750: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.750: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.750: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.750: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.750: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.751: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.751: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.751: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.752: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.752: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.752: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.752: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.752: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.753: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.753: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.753: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.753: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.753: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.753: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.753: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.753: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.753: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.753: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.754: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.754: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.754: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.754: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.755: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.755: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.755: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.755: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.755: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.755: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.755: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.755: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.755: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.755: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.755: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.756: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.756: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.756: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.756: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.757: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.757: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.757: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.757: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.758: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.758: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.758: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.758: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.758: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.758: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.758: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.758: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.758: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.758: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.758: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.759: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.759: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.760: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.760: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.760: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.760: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.761: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.761: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.761: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.761: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.761: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.761: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.761: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.761: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.761: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.761: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.761: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.762: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.762: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.762: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.762: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.763: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.763: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.763: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.763: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.763: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.763: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.763: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.763: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.763: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.763: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.763: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.764: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.764: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.764: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.764: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.765: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.765: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.765: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.765: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.766: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.766: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.766: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.766: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.766: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.766: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.766: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.766: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.766: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.766: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.766: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.766: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.767: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.767: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.767: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.768: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.768: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.768: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.768: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.768: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.768: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.768: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.768: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.768: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.768: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.768: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.768: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.768: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.769: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.769: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.769: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.770: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.770: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.770: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.770: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.770: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.770: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.770: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.770: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.770: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.770: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.770: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.770: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.771: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.771: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.771: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.772: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.772: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.772: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.773: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.773: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.773: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.773: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.773: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.773: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.773: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.773: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.773: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.773: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.773: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.773: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.774: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.774: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.774: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.775: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.775: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.775: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.775: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.775: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.775: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.775: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.775: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.775: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.775: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.776: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.776: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.776: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.776: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.776: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.776: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.777: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.777: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.777: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.778: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.778: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.778: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.778: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.778: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.778: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.778: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.778: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.778: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.778: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.778: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.778: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.778: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.779: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.779: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.780: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.780: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.780: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.780: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.780: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.780: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.780: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.780: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.781: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.781: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.781: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.781: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.781: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.781: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.781: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.781: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.782: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.782: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.782: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.782: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.782: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.783: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.783: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.783: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.783: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.783: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.783: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.783: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.783: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.783: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.783: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.783: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.784: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.784: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.784: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.784: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.785: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.785: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.785: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.785: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.785: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.785: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.785: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.785: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.785: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.785: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.785: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.785: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.785: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.786: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.786: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.786: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.786: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.787: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.787: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.787: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.787: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.787: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.787: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.787: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.787: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.787: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.787: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.787: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.787: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.788: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.788: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.788: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.788: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.789: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.789: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.789: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.789: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.789: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.789: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.789: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.789: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.789: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.789: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.789: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.789: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.790: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.790: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.790: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.790: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.791: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.791: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.791: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.791: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.791: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.791: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.791: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.791: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.791: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.791: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.791: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.791: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.791: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.792: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.792: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.792: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.792: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.793: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.793: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.794: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.794: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.794: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.794: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.794: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.794: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.794: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.794: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.794: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.794: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.794: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.794: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.794: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.795: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.795: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.795: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.796: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.796: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.796: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.796: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.796: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.796: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.796: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.796: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.796: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.796: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.796: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.796: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.797: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.797: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.797: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.797: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.798: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.798: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.799: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.799: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.799: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.799: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.799: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.799: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.799: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.799: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.799: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.799: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.799: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.799: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.799: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.800: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.800: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.800: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.800: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.801: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.801: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.801: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.801: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.801: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.801: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.801: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.801: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.801: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.801: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.801: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.802: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.802: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.802: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.802: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.803: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.803: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.803: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.803: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.804: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.804: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.804: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.804: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.804: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.804: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.804: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.804: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.804: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.804: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.804: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.805: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.805: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.805: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.805: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.806: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.806: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.806: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.806: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.806: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.806: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.806: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.806: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.806: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.806: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.806: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.806: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.806: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.807: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.807: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.807: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.808: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.808: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.808: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.808: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.808: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.808: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.808: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.808: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.808: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.808: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.808: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.808: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.809: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.809: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.809: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.809: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.810: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.810: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.810: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.810: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.811: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.811: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.811: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.811: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.811: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.811: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.811: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.811: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.811: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.811: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.811: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.811: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.812: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.812: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.812: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.813: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.813: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.813: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.813: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.813: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.813: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.813: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.813: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.813: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.813: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.813: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.813: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.814: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.814: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.814: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.814: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.815: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.815: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.815: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.815: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.815: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.815: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.815: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.815: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.815: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.815: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.815: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.815: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.816: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.816: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.816: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.816: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.817: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.817: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.817: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.817: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.818: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.818: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.818: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.818: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.818: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.818: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.818: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.818: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.818: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.818: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.818: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.819: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.819: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.819: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.819: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.820: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.820: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.820: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.820: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.820: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.820: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.820: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.820: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.820: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.820: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.820: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.820: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.821: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.821: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.821: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.822: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.822: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.822: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.822: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.823: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.823: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.823: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.823: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.823: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.823: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.823: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.823: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.823: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.823: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.823: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.824: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.824: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.824: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.824: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.825: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.825: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.825: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.825: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.825: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.825: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.825: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.825: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.825: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.825: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.825: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.825: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.825: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.826: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.826: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.826: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.826: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.827: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.827: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.827: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.827: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.827: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.827: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.827: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.827: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.827: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.827: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.827: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.827: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.827: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.828: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.828: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.828: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.828: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.829: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.829: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.829: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.829: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.829: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.829: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.829: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.829: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.829: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.829: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.829: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.829: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.830: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.830: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.830: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.830: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.831: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.831: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.831: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.831: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.831: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.831: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.831: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.831: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.831: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.831: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.831: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.831: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-device-DEBUG: 00:00:58.831: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.831: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.832: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.832: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.832: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.832: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.833: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.833: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.833: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.833: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.833: Finger status (picture number, mean) : 1 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.833: Finger status (picture number, mean) : 2 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.833: Finger status (picture number, mean) : 3 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.833: Finger status (picture number, mean) : 4 , 0 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.833: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.833: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.833: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.833: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.834: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.834: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.834: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.834: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.835: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.835: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.835: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.835: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.835: Finger status (picture number, mean) : 0 , 0 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.835: Finger status (picture number, mean) : 1 , 1 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.835: Finger status (picture number, mean) : 2 , 2 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.835: Finger status (picture number, mean) : 3 , 3 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.835: Finger status (picture number, mean) : 4 , 6 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.835: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.835: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.835: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.835: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.836: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.836: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.836: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.836: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.837: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.837: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.838: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.838: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.838: Finger status (picture number, mean) : 0 , 11 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.838: Finger status (picture number, mean) : 1 , 16 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.838: Finger status (picture number, mean) : 2 , 23 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.838: Finger status (picture number, mean) : 3 , 28 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.838: Finger status (picture number, mean) : 4 , 32 166s (process:2428): libfprint-device-DEBUG: 00:00:58.838: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.838: Image device reported finger status: on 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.838: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 166s (process:2428): libfprint-device-DEBUG: 00:00:58.838: Device reported finger status change: FP_FINGER_STATUS_NEEDED 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.838: Image device reported finger status: off 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.838: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.838: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.838: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.838: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.838: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.839: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.839: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.839: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.839: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.840: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.840: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.840: Finger status (picture number, mean) : 0 , 38 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.840: Finger status (picture number, mean) : 1 , 43 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.840: Finger status (picture number, mean) : 2 , 48 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.840: Finger status (picture number, mean) : 3 , 54 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.840: Finger status (picture number, mean) : 4 , 58 166s (process:2428): libfprint-device-DEBUG: 00:00:58.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.840: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.840: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.840: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.840: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.840: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.840: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.841: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.841: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.841: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.842: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.842: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.842: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.842: Finger status (picture number, mean) : 0 , 62 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.842: Finger status (picture number, mean) : 1 , 68 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.842: Finger status (picture number, mean) : 2 , 71 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.842: Finger status (picture number, mean) : 3 , 73 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.842: Finger status (picture number, mean) : 4 , 77 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.842: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.842: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.842: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.842: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.843: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.843: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.843: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.844: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.844: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.844: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.845: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.845: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.845: Finger status (picture number, mean) : 0 , 79 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.845: Finger status (picture number, mean) : 1 , 79 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.845: Finger status (picture number, mean) : 2 , 82 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.845: Finger status (picture number, mean) : 3 , 84 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.845: Finger status (picture number, mean) : 4 , 85 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.845: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.845: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.845: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.845: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.845: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.845: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.846: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.846: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.846: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.846: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.847: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.847: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.847: Finger status (picture number, mean) : 0 , 88 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.847: Finger status (picture number, mean) : 1 , 89 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.847: Finger status (picture number, mean) : 2 , 90 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.847: Finger status (picture number, mean) : 3 , 92 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.847: Finger status (picture number, mean) : 4 , 92 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.847: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.847: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.847: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.847: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.847: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.848: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.848: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.848: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.848: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.849: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.849: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.849: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.849: Finger status (picture number, mean) : 0 , 93 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.849: Finger status (picture number, mean) : 1 , 94 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.849: Finger status (picture number, mean) : 2 , 95 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.849: Finger status (picture number, mean) : 3 , 96 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.849: Finger status (picture number, mean) : 4 , 97 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.849: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.849: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.849: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.849: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.850: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.850: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.850: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.851: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.851: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.851: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.852: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.852: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.852: Finger status (picture number, mean) : 0 , 97 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.852: Finger status (picture number, mean) : 1 , 95 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.852: Finger status (picture number, mean) : 2 , 95 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.852: Finger status (picture number, mean) : 3 , 96 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.852: Finger status (picture number, mean) : 4 , 97 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.852: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.852: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.852: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.852: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.852: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.852: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.853: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.853: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.853: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.853: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.854: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.854: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.854: Finger status (picture number, mean) : 0 , 96 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.854: Finger status (picture number, mean) : 1 , 97 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.854: Finger status (picture number, mean) : 2 , 98 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.854: Finger status (picture number, mean) : 3 , 98 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.854: Finger status (picture number, mean) : 4 , 98 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.854: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.854: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.854: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.854: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.854: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.854: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.855: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.855: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.855: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.856: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.856: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.856: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.856: Finger status (picture number, mean) : 0 , 98 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.856: Finger status (picture number, mean) : 1 , 99 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.856: Finger status (picture number, mean) : 2 , 100 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.856: Finger status (picture number, mean) : 3 , 99 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.856: Finger status (picture number, mean) : 4 , 97 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.856: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.856: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.856: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.856: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.856: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.857: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.857: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.857: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.857: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.858: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.858: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.858: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.858: Finger status (picture number, mean) : 0 , 98 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.858: Finger status (picture number, mean) : 1 , 98 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.858: Finger status (picture number, mean) : 2 , 98 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.858: Finger status (picture number, mean) : 3 , 95 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.858: Finger status (picture number, mean) : 4 , 91 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.858: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.858: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.858: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.858: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.859: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.859: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.859: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.859: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.860: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.860: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.860: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.860: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.861: Finger status (picture number, mean) : 0 , 88 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.861: Finger status (picture number, mean) : 1 , 88 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.861: Finger status (picture number, mean) : 2 , 88 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.861: Finger status (picture number, mean) : 3 , 87 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.861: Finger status (picture number, mean) : 4 , 89 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.861: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.861: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.861: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.861: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.861: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.861: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.862: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.862: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.862: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.862: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.863: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.863: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.863: Finger status (picture number, mean) : 0 , 88 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.863: Finger status (picture number, mean) : 1 , 89 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.863: Finger status (picture number, mean) : 2 , 90 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.863: Finger status (picture number, mean) : 3 , 91 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.863: Finger status (picture number, mean) : 4 , 89 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.863: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.863: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.863: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.863: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.863: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.864: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.864: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.864: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.865: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.865: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.865: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.865: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.866: Finger status (picture number, mean) : 0 , 90 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.866: Finger status (picture number, mean) : 1 , 89 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.866: Finger status (picture number, mean) : 2 , 85 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.866: Finger status (picture number, mean) : 3 , 75 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.866: Finger status (picture number, mean) : 4 , 46 166s (process:2428): libfprint-image_device-DEBUG: 00:00:58.866: Image device reported finger status: on 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.866: [egis0570] SM_STATES_NUM entering state 5 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.866: [egis0570] SM_STATES_NUM entering state 1 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.866: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.866: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.866: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.867: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.867: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.867: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.867: [egis0570] SM_STATES_NUM entering state 2 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.868: [egis0570] SM_STATES_NUM entering state 3 166s (process:2428): libfprint-SSM-DEBUG: 00:00:58.868: [egis0570] SM_STATES_NUM entering state 4 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.868: Finger status (picture number, mean) : 0 , 17 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.868: Finger status (picture number, mean) : 1 , 14 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.868: Finger status (picture number, mean) : 2 , 15 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.868: Finger status (picture number, mean) : 3 , 15 166s (process:2428): libfprint-egis0570-DEBUG: 00:00:58.868: Finger status (picture number, mean) : 4 , 15 166s (process:2428): libfprint-assembling-DEBUG: 00:00:58.918: calc delta completed in 0.049543 secs 166s (process:2428): libfprint-assembling-DEBUG: 00:00:58.968: calc delta completed in 0.049761 secs 166s (process:2428): libfprint-assembling-DEBUG: 00:00:58.968: errors: 10243 rev: 29954 167s (process:2428): libfprint-assembling-DEBUG: 00:00:59.017: calc delta completed in 0.049666 secs 167s (process:2428): libfprint-assembling-DEBUG: 00:00:59.017: height is 292 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.019: Image device captured an image 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 167s (process:2428): libfprint-device-DEBUG: 00:00:59.020: Device reported finger status change: FP_FINGER_STATUS_PRESENT 167s (process:2428): libfprint-device-DEBUG: 00:00:59.020: Device reported finger status change: FP_FINGER_STATUS_NONE 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.020: Image device reported finger status: off 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.020: Deactivating image device 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 167s (process:2428): libfprint-SSM-DEBUG: 00:00:59.020: [egis0570] SM_STATES_NUM entering state 5 167s (process:2428): libfprint-SSM-DEBUG: 00:00:59.020: [egis0570] SM_STATES_NUM entering state 1 167s (process:2428): libfprint-egis0570-DEBUG: 00:00:59.020: deactivating, marking completed 167s (process:2428): libfprint-SSM-DEBUG: 00:00:59.020: [egis0570] SM_STATES_NUM completed successfully 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.020: Image device deactivation completed 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.020: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 167s (process:2428): libfprint-image-DEBUG: 00:00:59.081: Minutiae scan completed in 0.061275 secs 167s (process:2428): libfprint-device-DEBUG: 00:00:59.081: Device reported capture completion 167s (process:2428): libfprint-device-DEBUG: 00:00:59.081: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 167s (process:2428): libfprint-device-DEBUG: 00:00:59.081: Updated temperature model after 0.25 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 167s (process:2428): libfprint-image_device-DEBUG: 00:00:59.082: Image device close completed 167s (process:2428): libfprint-device-DEBUG: 00:00:59.082: Device reported close completion 167s (process:2428): libfprint-device-DEBUG: 00:00:59.082: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s (process:2428): libfprint-device-DEBUG: 00:00:59.082: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 167s ** (umockdev-run:2424): DEBUG: 00:00:59.342: umockdev.vala:154: Removing test bed /tmp/umockdev.4MFF22 167s (umockdev-run:2424): GLib-DEBUG: 00:00:59.344: unsetenv() is not thread-safe and should not be used after threads are created 167s Comparing PNGs /tmp/libfprint-umockdev-test-fxhjl_5z/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 167s PASS: libfprint-2/driver-egis0570.test 167s Running test: libfprint-2/virtual-device.test 167s (process:2435): libfprint-context-DEBUG: 00:00:59.483: Initializing FpContext (libfprint version 1.94.8+tod1) 167s (process:2435): libfprint-tod-DEBUG: 00:00:59.483: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 167s (process:2435): libfprint-context-DEBUG: 00:00:59.484: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-gbwhn0ig/virtual-device.socket 167s (process:2435): libfprint-context-DEBUG: 00:00:59.484: created 167s (process:2435): libfprint-device-DEBUG: 00:00:59.484: Device reported probe completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.484: Completing action FPI_DEVICE_ACTION_PROBE in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.484: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.484: 52406002: ../libfprint/drivers/virtual-device.c:387 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.484: 52406047: ../libfprint/drivers/virtual-device-listener.c:153 167s (process:2435): libfprint-device-DEBUG: 00:00:59.484: Device reported open completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.484: Completing action FPI_DEVICE_ACTION_OPEN in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.484: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.485: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Got instructions of length 16 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Received command SET_KEEP_ALIVE 0 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Keep alive toggled: 0 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.485: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Got instructions of length 19 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Received command SET_ENROLL_STAGES 5 167s (process:2435): libfprint-device-DEBUG: 00:00:59.485: Device reported close completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.485: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.485: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s ok 167s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: 52406717: ../libfprint/drivers/virtual-device.c:387 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.485: 52406725: ../libfprint/drivers/virtual-device-listener.c:153 167s (process:2435): libfprint-device-DEBUG: 00:00:59.485: Device reported open completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.485: Completing action FPI_DEVICE_ACTION_OPEN in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.485: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.485: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Got instructions of length 20 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Received command SET_ENROLL_STAGES 20 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.485: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Got instructions of length 19 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Received command SET_ENROLL_STAGES 1 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.485: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Got instructions of length 19 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.485: Received command SET_ENROLL_STAGES 0 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.487: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Got instructions of length 16 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Received command SET_KEEP_ALIVE 0 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Keep alive toggled: 0 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.487: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Got instructions of length 19 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Received command SET_ENROLL_STAGES 5 167s (process:2435): libfprint-device-DEBUG: 00:00:59.487: Device reported close completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.487: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.487: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s ok 167s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: 52409001: ../libfprint/drivers/virtual-device.c:387 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.487: 52409013: ../libfprint/drivers/virtual-device-listener.c:153 167s (process:2435): libfprint-device-DEBUG: 00:00:59.487: Device reported open completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.487: Completing action FPI_DEVICE_ACTION_OPEN in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.487: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.487: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Got instructions of length 19 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Received command SET_SCAN_TYPE press 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.487: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Got instructions of length 19 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.487: Received command SET_SCAN_TYPE swipe 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.488: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Got instructions of length 25 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Received command SET_SCAN_TYPE eye-contact 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.488: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Got instructions of length 16 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Received command SET_KEEP_ALIVE 0 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Keep alive toggled: 0 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.488: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Got instructions of length 19 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Received command SET_ENROLL_STAGES 5 167s (process:2435): libfprint-device-DEBUG: 00:00:59.488: Device reported close completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.488: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.488: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s ok 167s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: 52409806: ../libfprint/drivers/virtual-device.c:387 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.488: 52409817: ../libfprint/drivers/virtual-device-listener.c:153 167s (process:2435): libfprint-device-DEBUG: 00:00:59.488: Device reported open completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.488: Completing action FPI_DEVICE_ACTION_OPEN in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.488: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.488: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Got instructions of length 9 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Received command SLEEP 100 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.488: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Got instructions of length 7 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Received command ERROR 4 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Processing command SLEEP 100 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.488: Sleeping 100ms 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.589: Sleeping completed 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.589: Processing command ERROR 4 167s (process:2435): libfprint-device-DEBUG: 00:00:59.589: Device reported close completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.589: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.589: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s ok 167s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.589: 52511306: ../libfprint/drivers/virtual-device.c:387 167s (process:2435): libfprint-device-DEBUG: 00:00:59.589: Device reported open completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.589: Completing action FPI_DEVICE_ACTION_OPEN in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.589: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.590: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.590: Got instructions of length 16 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.590: Received command SET_KEEP_ALIVE 1 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.590: Keep alive toggled: 1 167s (process:2435): libfprint-device-DEBUG: 00:00:59.590: Device reported close completion 167s (process:2435): libfprint-device-DEBUG: 00:00:59.590: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s (process:2435): libfprint-device-DEBUG: 00:00:59.590: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 167s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:00:59.590: Got a new connection! 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.590: Got instructions of length 9 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.590: Received command SLEEP 500 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.590: 52511677: ../libfprint/drivers/virtual-device.c:387 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.590: Processing command SLEEP 500 167s (process:2435): libfprint-virtual_device-DEBUG: 00:00:59.590: Sleeping 500ms 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.090: Sleeping completed 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.091: 53012449: ../libfprint/drivers/virtual-device.c:387 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Device reported open completion 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Completing action FPI_DEVICE_ACTION_OPEN in idle! 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.091: Got a new connection! 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.091: Got instructions of length 16 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.091: Received command SET_KEEP_ALIVE 0 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.091: Keep alive toggled: 0 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.091: Got a new connection! 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.091: Got instructions of length 19 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.091: Received command SET_ENROLL_STAGES 5 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Device reported close completion 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s ok 168s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.091: 53013259: ../libfprint/drivers/virtual-device.c:387 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.091: 53013270: ../libfprint/drivers/virtual-device-listener.c:153 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Device reported open completion 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Completing action FPI_DEVICE_ACTION_OPEN in idle! 168s (process:2435): libfprint-device-DEBUG: 00:01:00.091: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.092: Got a new connection! 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.092: Got instructions of length 16 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.092: Received command IGNORED_COMMAND 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.092: Got a new connection! 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.092: Got instructions of length 9 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.092: Received command SLEEP 500 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.092: Processing command IGNORED_COMMAND 168s (process:2435): libfprint-device-DEBUG: 00:01:00.092: Device reported close completion 168s (process:2435): libfprint-device-DEBUG: 00:01:00.092: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 168s (process:2435): libfprint-device-DEBUG: 00:01:00.092: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.092: 53013738: ../libfprint/drivers/virtual-device.c:387 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.092: Processing command SLEEP 500 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.092: Sleeping 500ms 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.593: Sleeping completed 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.593: 53514522: ../libfprint/drivers/virtual-device.c:387 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.593: 53514544: ../libfprint/drivers/virtual-device-listener.c:153 168s (process:2435): libfprint-device-DEBUG: 00:01:00.593: Device reported open completion 168s (process:2435): libfprint-device-DEBUG: 00:01:00.593: Completing action FPI_DEVICE_ACTION_OPEN in idle! 168s (process:2435): libfprint-device-DEBUG: 00:01:00.593: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.593: Got a new connection! 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.593: Got instructions of length 16 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.593: Received command SET_KEEP_ALIVE 0 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.593: Keep alive toggled: 0 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.593: Got a new connection! 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.593: Got instructions of length 19 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.593: Received command SET_ENROLL_STAGES 5 168s (process:2435): libfprint-device-DEBUG: 00:01:00.593: Device reported close completion 168s (process:2435): libfprint-device-DEBUG: 00:01:00.593: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 168s (process:2435): libfprint-device-DEBUG: 00:01:00.593: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s ok 168s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.593: 53515366: ../libfprint/drivers/virtual-device.c:387 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.593: 53515374: ../libfprint/drivers/virtual-device-listener.c:153 168s (process:2435): libfprint-device-DEBUG: 00:01:00.593: Device reported open completion 168s (process:2435): libfprint-device-DEBUG: 00:01:00.594: Completing action FPI_DEVICE_ACTION_OPEN in idle! 168s (process:2435): libfprint-device-DEBUG: 00:01:00.594: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.594: Got a new connection! 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.594: Got instructions of length 16 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.594: Received command SET_KEEP_ALIVE 1 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.594: Keep alive toggled: 1 168s (process:2435): libfprint-device-DEBUG: 00:01:00.594: Device reported close completion 168s (process:2435): libfprint-device-DEBUG: 00:01:00.594: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 168s (process:2435): libfprint-device-DEBUG: 00:01:00.594: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:00.594: Got a new connection! 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.594: Got instructions of length 9 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.594: Received command SLEEP 500 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.594: 53515627: ../libfprint/drivers/virtual-device.c:387 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.594: Processing command SLEEP 500 168s (process:2435): libfprint-virtual_device-DEBUG: 00:01:00.594: Sleeping 500ms 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.094: Sleeping completed 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.094: 54016409: ../libfprint/drivers/virtual-device.c:387 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Device reported open completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Completing action FPI_DEVICE_ACTION_OPEN in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.095: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.095: Got instructions of length 16 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.095: Received command SET_KEEP_ALIVE 0 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.095: Keep alive toggled: 0 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.095: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.095: Got instructions of length 19 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.095: Received command SET_ENROLL_STAGES 5 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Device reported close completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s ok 169s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.095: 54017187: ../libfprint/drivers/virtual-device.c:387 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.095: 54017197: ../libfprint/drivers/virtual-device-listener.c:153 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Device reported open completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Completing action FPI_DEVICE_ACTION_OPEN in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.095: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.096: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Got instructions of length 16 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Received command SET_KEEP_ALIVE 0 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Keep alive toggled: 0 169s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 169s self.assertFalse(self.dev.supports_identify()) 169s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 169s self.assertFalse(self.dev.supports_capture()) 169s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 169s self.assertFalse(self.dev.has_storage()) 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.096: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Got instructions of length 19 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Received command SET_ENROLL_STAGES 5 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Device reported close completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s ok 169s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: 54017714: ../libfprint/drivers/virtual-device.c:387 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.096: 54017722: ../libfprint/drivers/virtual-device-listener.c:153 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Device reported open completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Completing action FPI_DEVICE_ACTION_OPEN in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.096: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Got instructions of length 16 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Received command SET_KEEP_ALIVE 0 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Keep alive toggled: 0 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.096: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Got instructions of length 19 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Received command SET_ENROLL_STAGES 5 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Device reported close completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s ok 169s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: 54018150: ../libfprint/drivers/virtual-device.c:387 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.096: 54018161: ../libfprint/drivers/virtual-device-listener.c:153 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Device reported open completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Completing action FPI_DEVICE_ACTION_OPEN in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.096: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.096: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Got instructions of length 10 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.096: Received command SLEEP 1500 169s (process:2435): libfprint-device-DEBUG: 00:01:01.097: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.097: Processing command SLEEP 1500 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.097: Sleeping 1500ms 169s (process:2435): libfprint-device-DEBUG: 00:01:01.394: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 169s (process:2435): libfprint-device-DEBUG: 00:01:01.397: Idle cancelling on ongoing operation! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.397: Got cancellation! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.397: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.397: Virtual device scan failed with error: Operation was cancelled 169s (process:2435): libfprint-device-DEBUG: 00:01:01.397: Device reported verify completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.397: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:2435): libfprint-device-DEBUG: 00:01:01.397: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.397: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.597: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.597: Got instructions of length 16 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.597: Received command SET_KEEP_ALIVE 0 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.597: Keep alive toggled: 0 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.597: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.597: Got instructions of length 19 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.597: Received command SET_ENROLL_STAGES 5 169s (process:2435): libfprint-device-DEBUG: 00:01:01.597: Device reported close completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s ok 169s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: 54519538: ../libfprint/drivers/virtual-device.c:387 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.598: 54519551: ../libfprint/drivers/virtual-device-listener.c:153 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported open completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Completing action FPI_DEVICE_ACTION_OPEN in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.598: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Got instructions of length 14 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Received command SCAN foo-print 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Processing command SCAN foo-print 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported enroll progress, reported 1 of 5 have been completed 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Sleeping completed 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.598: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Got instructions of length 14 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Received command SCAN foo-print 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Processing command SCAN foo-print 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported enroll progress, reported 2 of 5 have been completed 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Sleeping completed 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.598: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Got instructions of length 14 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Received command SCAN foo-print 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.598: Processing command SCAN foo-print 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-device-DEBUG: 00:01:01.598: Device reported enroll progress, reported 3 of 5 have been completed 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Sleeping completed 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.599: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Got instructions of length 14 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Received command SCAN foo-print 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Processing command SCAN foo-print 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Device reported enroll progress, reported 4 of 5 have been completed 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Sleeping completed 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.599: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Got instructions of length 14 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Received command SCAN foo-print 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Processing command SCAN foo-print 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Device reported enroll progress, reported 5 of 5 have been completed 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Device reported enroll completion 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Print for finger FP_FINGER_LEFT_RING enrolled 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.599: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Got instructions of length 9 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Received command SLEEP 100 169s (process:2435): libfprint-device-DEBUG: 00:01:01.599: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Processing command SLEEP 100 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Sleeping 100ms 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.599: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Got instructions of length 14 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Received command SCAN bar-print 169s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:01.599: Got a new connection! 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Got instructions of length 9 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.599: Received command SLEEP 800 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.699: Sleeping completed 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.699: Processing command SCAN bar-print 169s (process:2435): libfprint-device-DEBUG: 00:01:01.699: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-device-DEBUG: 00:01:01.699: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.699: Virtual device scanned print bar-print 169s (process:2435): libfprint-device-DEBUG: 00:01:01.699: Device reported verify result 169s (process:2435): libfprint-device-DEBUG: 00:01:01.699: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.699: Processing command SLEEP 800 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.699: Sleeping 800ms 169s (process:2435): libfprint-virtual_device-DEBUG: 00:01:01.699: Sleeping now, command queued for later: SCAN bar-print 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.500: Sleeping completed 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.500: Processing command SCAN bar-print 170s (process:2435): libfprint-device-DEBUG: 00:01:02.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.500: Virtual device scanned print bar-print 170s (process:2435): libfprint-device-DEBUG: 00:01:02.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED 170s (process:2435): libfprint-device-DEBUG: 00:01:02.500: Device reported verify completion 170s (process:2435): libfprint-device-DEBUG: 00:01:02.500: Device reported finger status change: FP_FINGER_STATUS_NONE 170s (process:2435): libfprint-device-DEBUG: 00:01:02.501: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s (process:2435): libfprint-device-DEBUG: 00:01:02.501: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:02.501: Got a new connection! 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Got instructions of length 16 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Received command SET_KEEP_ALIVE 0 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Keep alive toggled: 0 170s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:02.501: Got a new connection! 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Got instructions of length 19 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Received command SET_ENROLL_STAGES 5 170s (process:2435): libfprint-device-DEBUG: 00:01:02.501: Device reported close completion 170s (process:2435): libfprint-device-DEBUG: 00:01:02.501: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s (process:2435): libfprint-device-DEBUG: 00:01:02.501: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s Enroll done 170s ok 170s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: 55423047: ../libfprint/drivers/virtual-device.c:387 170s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:02.501: 55423058: ../libfprint/drivers/virtual-device-listener.c:153 170s (process:2435): libfprint-device-DEBUG: 00:01:02.501: Device reported open completion 170s (process:2435): libfprint-device-DEBUG: 00:01:02.501: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s (process:2435): libfprint-device-DEBUG: 00:01:02.501: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:02.501: Got a new connection! 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Got instructions of length 26 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Received command SET_CANCELLATION_ENABLED 0 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Cancellation support toggled: 0 170s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:02.501: Got a new connection! 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Got instructions of length 10 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Received command SLEEP 1500 170s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:02.501: Got a new connection! 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Got instructions of length 14 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.501: Received command SCAN foo-print 170s (process:2435): libfprint-device-DEBUG: 00:01:02.502: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.502: Processing command SLEEP 1500 170s (process:2435): libfprint-virtual_device-DEBUG: 00:01:02.502: Sleeping 1500ms 170s (process:2435): libfprint-device-DEBUG: 00:01:02.802: Idle cancelling on ongoing operation! 171s Executing: libfprint-2/virtual-device.test 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.003: Sleeping completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.003: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.003: Virtual device scan failed with error: Operation was cancelled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.003: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.003: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.003: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.003: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.003: Processing command SCAN foo-print 172s (process:2435): libfprint-device-DEBUG: 00:01:04.003: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.003: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.003: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.003: 56925390: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.003: 56925401: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.004: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Received command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported enroll progress, reported 1 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.004: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported enroll progress, reported 2 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.004: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported enroll progress, reported 3 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.004: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported enroll progress, reported 4 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.004: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported enroll progress, reported 5 of 5 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Print for finger FP_FINGER_LEFT_LITTLE enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.004: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.004: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.004: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.005: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.005: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.005: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s Enroll done 172s ok 172s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: 56926560: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: 56926567: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.005: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.005: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.005: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SET_ENROLL_STAGES 8 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command RETRY 1 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command RETRY 3 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command RETRY 2 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SLEEP 10 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SLEEP 20 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command RETRY 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command RETRY 3 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.005: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.005: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.006: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Got instructions of length 15 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Received command SCAN another-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.006: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.006: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Received command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported enroll progress, reported 1 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported enroll progress, reported 2 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command RETRY 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported enroll progress, reported 2 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported enroll progress, reported 3 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command RETRY 3 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported enroll progress, reported 3 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported enroll progress, reported 4 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command RETRY 2 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported enroll progress, reported 4 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.006: Device reported enroll progress, reported 5 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Processing command SLEEP 10 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.006: Sleeping 10ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.016: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.016: Processing command SLEEP 20 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.016: Sleeping 20ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Processing command RETRY 0 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported enroll progress, reported 5 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Processing command RETRY 3 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported enroll progress, reported 5 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported enroll progress, reported 6 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Processing command SCAN another-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported enroll progress, reported 6 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported enroll progress, reported 7 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.036: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported enroll progress, reported 8 of 8 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Print for finger FP_FINGER_UNKNOWN enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.036: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.037: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.037: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.037: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: 56958649: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: 56958669: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.037: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.037: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.037: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SLEEP 50 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command RETRY 1 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SLEEP 50 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command RETRY 2 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 15 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SCAN another-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.037: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Received command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.037: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Processing command SLEEP 50 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.037: Sleeping 50ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported enroll progress, reported 1 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported enroll progress, reported 2 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Processing command RETRY 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported enroll progress, reported 2 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.088: Device reported enroll progress, reported 3 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Processing command SLEEP 50 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.088: Sleeping 50ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.138: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.138: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported enroll progress, reported 4 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.138: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.138: Processing command RETRY 2 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported enroll progress, reported 4 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.138: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.138: Processing command SCAN another-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported enroll progress, reported 4 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.138: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.138: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported enroll progress, reported 5 of 5 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Print for finger FP_FINGER_UNKNOWN enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.138: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.139: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.139: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: 57060833: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.139: 57060842: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.139: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Received command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported enroll progress, reported 1 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.139: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported enroll progress, reported 2 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.139: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported enroll progress, reported 3 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.139: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.139: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported enroll progress, reported 4 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.140: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported enroll progress, reported 5 of 5 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Print for finger FP_FINGER_LEFT_RING enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.140: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Received command ERROR 0 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Processing command ERROR 0 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Virtual device scan failed with error: An unspecified error occurred! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.140: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.140: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s Enroll done 172s ok 172s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: 57062030: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.140: 57062039: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.140: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Received command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported enroll progress, reported 1 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.140: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported enroll progress, reported 2 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.140: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.140: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported enroll progress, reported 3 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.141: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported enroll progress, reported 4 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.141: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported enroll progress, reported 5 of 5 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Print for finger FP_FINGER_LEFT_THUMB enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.141: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Received command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Virtual device scanned print testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported verify result 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.141: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.141: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s Enroll done 172s ok 172s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: 57063117: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.141: 57063126: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.141: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Received command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported enroll progress, reported 1 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.141: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.141: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.141: Device reported enroll progress, reported 2 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.142: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported enroll progress, reported 3 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.142: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported enroll progress, reported 4 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.142: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported enroll progress, reported 5 of 5 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Print for finger FP_FINGER_LEFT_RING enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.142: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Got instructions of length 18 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Received command SCAN not-testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Processing command SCAN not-testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Virtual device scanned print not-testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported verify result 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.142: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.142: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s Enroll done 172s ok 172s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: 57064186: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.142: 57064194: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.142: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Received command RETRY 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Processing command RETRY 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.142: Virtual device scan failed with error: The swipe was too short, please try again. 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported verify result 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.142: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.143: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.143: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.143: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: 57064623: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: 57064630: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.143: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.143: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.143: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SET_ENROLL_STAGES 8 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command RETRY 1 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command RETRY 3 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command RETRY 2 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SLEEP 10 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command SLEEP 20 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command RETRY 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.143: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.143: Received command RETRY 3 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.144: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.144: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Got instructions of length 15 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Received command SCAN another-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.144: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Received command SCAN print-id 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.144: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Received command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported enroll progress, reported 1 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported enroll progress, reported 2 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command RETRY 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported enroll progress, reported 2 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported enroll progress, reported 3 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command RETRY 3 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported enroll progress, reported 3 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported enroll progress, reported 4 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command RETRY 2 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported enroll progress, reported 4 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.144: Device reported enroll progress, reported 5 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Processing command SLEEP 10 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.144: Sleeping 10ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.154: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.154: Processing command SLEEP 20 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.154: Sleeping 20ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Processing command RETRY 0 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported enroll progress, reported 5 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Processing command RETRY 3 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported enroll progress, reported 5 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported enroll progress, reported 6 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Processing command SCAN another-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported enroll progress, reported 6 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported enroll progress, reported 7 of 8 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.174: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported enroll progress, reported 8 of 8 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Print for finger FP_FINGER_UNKNOWN enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.174: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.175: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Received command RETRY 2 172s (process:2435): libfprint-device-DEBUG: 00:01:04.175: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Processing command RETRY 2 172s (process:2435): libfprint-device-DEBUG: 00:01:04.175: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Virtual device scan failed with error: The finger was not centered properly, please try again. 172s (process:2435): libfprint-device-DEBUG: 00:01:04.175: Device reported verify result 172s (process:2435): libfprint-device-DEBUG: 00:01:04.175: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.175: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.175: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.175: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.175: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Received command SLEEP 50 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.175: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Received command RETRY 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.175: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Processing command SLEEP 50 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.175: Sleeping 50ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.225: Sleeping completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.225: Processing command RETRY 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.225: Virtual device scan failed with error: The swipe was too short, please try again. 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Device reported verify result 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.225: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.225: Got instructions of length 15 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.225: Received command SCAN another-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.225: Processing command SCAN another-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Virtual device scanned print another-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported verify result 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.226: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Got instructions of length 13 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Received command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Processing command SCAN print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Virtual device scanned print print-id 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported verify result 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.226: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.226: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: 57147977: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.226: 57147986: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.226: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Received command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported enroll progress, reported 1 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.226: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.226: Device reported enroll progress, reported 2 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.226: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.226: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Received command RETRY 1 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Processing command RETRY 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported enroll progress, reported 2 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.227: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported enroll progress, reported 3 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.227: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported enroll progress, reported 4 of 5 have been completed 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Sleeping completed 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.227: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Received command SCAN testprint 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported enroll progress, reported 5 of 5 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Print for finger FP_FINGER_LEFT_LITTLE enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.227: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.227: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s Enroll done 172s ok 172s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: 57149085: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.227: 57149096: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.227: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Received command FINGER 1 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Processing command FINGER 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.227: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Received command FINGER 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Processing command FINGER 0 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Idle cancelling on ongoing operation! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Got cancellation! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.227: Virtual device scan failed with error: Operation was cancelled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.227: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.228: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.228: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.228: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.228: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.228: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: 57149621: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.228: 57149628: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.228: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.228: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.228: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.228: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Received command SLEEP 10 172s (process:2435): libfprint-device-DEBUG: 00:01:04.228: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Processing command SLEEP 10 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.228: Sleeping 10ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Sleeping completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.238: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Received command FINGER 1 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Processing command FINGER 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.238: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Got instructions of length 8 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Received command FINGER 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Processing command FINGER 0 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Idle cancelling on ongoing operation! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Got cancellation! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Virtual device scan failed with error: Operation was cancelled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Device reported verify completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.238: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.238: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.238: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.238: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: 57160415: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.239: 57160428: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.239: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.239: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: 57160831: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.239: 57160840: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.239: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Received command IGNORED_COMMAND 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.239: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Received command ERROR 5 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Processing command IGNORED_COMMAND 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: 57161198: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Processing command ERROR 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: 57161283: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.239: 57161292: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.239: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.239: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Received command SET_KEEP_ALIVE 1 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.239: Keep alive toggled: 1 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.240: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Got instructions of length 7 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Received command ERROR 5 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: 57161507: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Processing command ERROR 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s ok 172s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: 57161585: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.240: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Received command SET_ENROLL_STAGES 1 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.240: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Got instructions of length 14 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Received command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Processing command SCAN testprint 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported enroll progress, reported 1 of 1 have been completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported enroll completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported finger status change: FP_FINGER_STATUS_NONE 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Print for finger FP_FINGER_LEFT_LITTLE enrolled 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.240: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Got instructions of length 16 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Received command SET_KEEP_ALIVE 0 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Keep alive toggled: 0 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.240: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Got instructions of length 19 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.240: Received command SET_ENROLL_STAGES 5 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.240: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 172s Enroll done 172s ok 172s (process:2435): libfprint-context-DEBUG: 00:01:04.241: Initializing FpContext (libfprint version 1.94.8+tod1) 172s (process:2435): libfprint-tod-DEBUG: 00:01:04.241: 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:2435): libfprint-context-DEBUG: 00:01:04.241: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-0zy_awg1/virtual-device.socket 172s (process:2435): libfprint-context-DEBUG: 00:01:04.241: created 172s (process:2435): libfprint-device-DEBUG: 00:01:04.241: Device reported probe completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.241: Completing action FPI_DEVICE_ACTION_PROBE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.241: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.241: 57162986: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.241: 57162993: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.241: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.241: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.241: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.241: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.241: Got instructions of length 9 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.241: Received command SLEEP 200 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.241: Processing command SLEEP 200 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.241: Sleeping 200ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.442: Sleeping completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.442: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.442: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.442: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 172s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.442: 57364010: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.442: 57364045: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.442: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.442: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.442: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.442: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.442: Got instructions of length 9 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.442: Received command SLEEP 200 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.442: Processing command SLEEP 200 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.442: Sleeping 200ms 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.643: Sleeping completed 172s (process:2435): libfprint-device-DEBUG: 00:01:04.643: Device reported close completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.643: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.643: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s ok 172s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.643: 57565208: ../libfprint/drivers/virtual-device.c:387 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.643: 57565222: ../libfprint/drivers/virtual-device-listener.c:153 172s (process:2435): libfprint-device-DEBUG: 00:01:04.643: Device reported open completion 172s (process:2435): libfprint-device-DEBUG: 00:01:04.643: Completing action FPI_DEVICE_ACTION_OPEN in idle! 172s (process:2435): libfprint-device-DEBUG: 00:01:04.643: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 172s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.644: Got a new connection! 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.644: Got instructions of length 9 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.644: Received command SLEEP 200 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.644: Processing command SLEEP 200 172s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.644: Sleeping 200ms 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.844: Sleeping completed 173s (process:2435): libfprint-device-DEBUG: 00:01:04.844: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:04.844: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:04.844: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.845: 57766429: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.845: 57766441: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:04.845: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:04.845: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:04.845: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:04.845: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.845: Got instructions of length 9 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.845: Received command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.845: Processing command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:04.845: Sleeping 200ms 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.045: Sleeping completed 173s (process:2435): libfprint-device-DEBUG: 00:01:05.045: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.046: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.046: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.046: 57967676: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.046: 57967690: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.046: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.046: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.046: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.046: Got instructions of length 9 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.046: Received command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.046: Processing command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.046: Sleeping 200ms 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.246: Sleeping completed 173s (process:2435): libfprint-device-DEBUG: 00:01:05.247: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.247: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.247: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.247: 58169063: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.247: 58169094: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.247: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.247: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.247: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.247: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.248: Got instructions of length 9 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.248: Received command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.248: Processing command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.248: Sleeping 200ms 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.448: Sleeping completed 173s (process:2435): libfprint-device-DEBUG: 00:01:05.448: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.448: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.448: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.448: 58370367: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.448: 58370380: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.449: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.449: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.449: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.449: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.449: Got instructions of length 9 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.449: Received command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.449: Processing command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.449: Sleeping 200ms 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.449: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.449: Got instructions of length 16 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.449: Received command SET_KEEP_ALIVE 1 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.449: Keep alive toggled: 1 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.649: Sleeping completed 173s (process:2435): libfprint-device-DEBUG: 00:01:05.649: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.649: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.649: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.650: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.650: Got instructions of length 9 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.650: Received command SLEEP 100 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.650: 58571739: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.650: Processing command SLEEP 100 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.650: Sleeping 100ms 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.750: Sleeping completed 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.750: 58672118: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-device-DEBUG: 00:01:05.750: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.750: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.750: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.750: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.750: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.750: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.751: 58672641: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-device-DEBUG: 00:01:05.751: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.751: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.751: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.751: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.751: Got instructions of length 9 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.751: Received command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.751: Processing command SLEEP 200 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.751: Sleeping 200ms 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.951: Sleeping completed 173s (process:2435): libfprint-device-DEBUG: 00:01:05.952: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.952: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.952: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.952: 58874004: ../libfprint/drivers/virtual-device.c:752 173s (process:2435): libfprint-context-DEBUG: 00:01:05.952: Initializing FpContext (libfprint version 1.94.8+tod1) 173s (process:2435): libfprint-tod-DEBUG: 00:01:05.952: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 173s (process:2435): libfprint-context-DEBUG: 00:01:05.953: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-q7ke34sn/virtual-device.socket 173s (process:2435): libfprint-context-DEBUG: 00:01:05.953: created 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Device reported probe completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Completing action FPI_DEVICE_ACTION_PROBE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.953: 58874911: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.953: 58874919: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.953: 58875134: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.953: 58875143: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.953: 58875281: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.953: 58875289: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.954: 58875437: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.954: 58875446: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.954: 58875583: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.954: 58875591: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.954: 58875725: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.954: 58875734: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.954: 58875867: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.954: 58875875: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.954: 58876043: ../libfprint/drivers/virtual-device.c:752 173s (process:2435): libfprint-context-DEBUG: 00:01:05.954: Initializing FpContext (libfprint version 1.94.8+tod1) 173s (process:2435): libfprint-tod-DEBUG: 00:01:05.954: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 173s (process:2435): libfprint-context-DEBUG: 00:01:05.954: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-q7ke34sn/virtual-device.socket 173s (process:2435): libfprint-context-DEBUG: 00:01:05.954: created 173s (process:2435): libfprint-context-DEBUG: 00:01:05.954: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ybujci0r/virtual-device-storage.socket 173s (process:2435): libfprint-context-DEBUG: 00:01:05.954: created 173s (process:2435): libfprint-device-DEBUG: 00:01:05.954: Device reported probe completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Device reported probe completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Completing action FPI_DEVICE_ACTION_PROBE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Completing action FPI_DEVICE_ACTION_PROBE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: 58876661: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.955: 58876672: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.955: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Got instructions of length 5 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Received command CONT 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Processing command CONT 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Device reported deletion completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.955: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Got instructions of length 16 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Received command SET_KEEP_ALIVE 0 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Keep alive toggled: 0 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.955: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Got instructions of length 19 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Received command SET_ENROLL_STAGES 5 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: 58877171: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.955: 58877179: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.955: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.955: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Got instructions of length 20 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Received command SET_ENROLL_STAGES 20 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.955: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Got instructions of length 19 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.955: Received command SET_ENROLL_STAGES 1 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Got instructions of length 19 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Received command SET_ENROLL_STAGES 0 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Got instructions of length 5 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Received command CONT 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Processing command CONT 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Device reported deletion completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Got instructions of length 16 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Received command SET_KEEP_ALIVE 0 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Keep alive toggled: 0 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Got instructions of length 19 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Received command SET_ENROLL_STAGES 5 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: 58877920: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: 58877927: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Device reported open completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Completing action FPI_DEVICE_ACTION_OPEN in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Got instructions of length 19 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Received command SET_SCAN_TYPE press 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Got instructions of length 19 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Received command SET_SCAN_TYPE swipe 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Got instructions of length 25 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Received command SET_SCAN_TYPE eye-contact 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Got instructions of length 5 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Received command CONT 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.956: Processing command CONT 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Device reported deletion completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.956: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: Got instructions of length 16 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: Received command SET_KEEP_ALIVE 0 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: Keep alive toggled: 0 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.957: Got a new connection! 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: Got instructions of length 19 173s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: Received command SET_ENROLL_STAGES 5 173s (process:2435): libfprint-device-DEBUG: 00:01:05.957: Device reported close completion 173s (process:2435): libfprint-device-DEBUG: 00:01:05.957: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 173s (process:2435): libfprint-device-DEBUG: 00:01:05.957: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 173s ok 173s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: 58878581: ../libfprint/drivers/virtual-device.c:387 173s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.957: 58878589: ../libfprint/drivers/virtual-device-listener.c:153 173s (process:2435): libfprint-device-DEBUG: 00:01:05.957: Device reported open completion 174s (process:2435): libfprint-device-DEBUG: 00:01:05.957: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:2435): libfprint-device-DEBUG: 00:01:05.957: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:05.957: Got a new connection! 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: Got instructions of length 9 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: Received command INSERT p1 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:05.957: Processing command INSERT p1 174s (process:2435): libfprint-device-DEBUG: 00:01:06.457: Device reported listing completion 174s (process:2435): libfprint-device-DEBUG: 00:01:06.458: Completing action FPI_DEVICE_ACTION_LIST in idle! 174s (process:2435): libfprint-device-DEBUG: 00:01:06.458: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:06.458: Got a new connection! 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.458: Got instructions of length 5 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.458: Received command CONT 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.458: Processing command CONT 174s (process:2435): libfprint-device-DEBUG: 00:01:06.458: Device reported deletion completion 174s (process:2435): libfprint-device-DEBUG: 00:01:06.458: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 174s (process:2435): libfprint-device-DEBUG: 00:01:06.458: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:2435): libfprint-device-DEBUG: 00:01:06.959: Device reported listing completion 174s (process:2435): libfprint-device-DEBUG: 00:01:06.959: Completing action FPI_DEVICE_ACTION_LIST in idle! 174s (process:2435): libfprint-device-DEBUG: 00:01:06.959: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:06.959: Got a new connection! 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.959: Got instructions of length 5 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.959: Received command CONT 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.959: Processing command CONT 174s (process:2435): libfprint-device-DEBUG: 00:01:06.959: Device reported deletion completion 174s (process:2435): libfprint-device-DEBUG: 00:01:06.959: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 174s (process:2435): libfprint-device-DEBUG: 00:01:06.959: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:06.959: Got a new connection! 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.959: Got instructions of length 16 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.959: Received command SET_KEEP_ALIVE 0 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.959: Keep alive toggled: 0 174s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:06.959: Got a new connection! 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.959: Got instructions of length 19 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.959: Received command SET_ENROLL_STAGES 5 174s (process:2435): libfprint-device-DEBUG: 00:01:06.959: Device reported close completion 174s (process:2435): libfprint-device-DEBUG: 00:01:06.960: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 174s (process:2435): libfprint-device-DEBUG: 00:01:06.960: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s 174s ok 174s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.960: 59881536: ../libfprint/drivers/virtual-device.c:387 174s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:06.960: 59881545: ../libfprint/drivers/virtual-device-listener.c:153 174s (process:2435): libfprint-device-DEBUG: 00:01:06.960: Device reported open completion 174s (process:2435): libfprint-device-DEBUG: 00:01:06.960: Completing action FPI_DEVICE_ACTION_OPEN in idle! 174s (process:2435): libfprint-device-DEBUG: 00:01:06.960: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 174s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:06.960: Got a new connection! 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.960: Got instructions of length 9 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.960: Received command INSERT p1 174s (process:2435): libfprint-virtual_device-DEBUG: 00:01:06.960: Processing command INSERT p1 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Device reported listing completion 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Completing action FPI_DEVICE_ACTION_LIST in idle! 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.461: Got a new connection! 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Got instructions of length 7 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Received command ERROR 5 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Processing command ERROR 5 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Device reported deletion completion 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.461: Got a new connection! 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Got instructions of length 5 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Received command CONT 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Processing command CONT 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Device reported deletion completion 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 175s (process:2435): libfprint-device-DEBUG: 00:01:07.461: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.461: Got a new connection! 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Got instructions of length 16 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Received command SET_KEEP_ALIVE 0 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Keep alive toggled: 0 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.461: Got a new connection! 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Got instructions of length 19 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.461: Received command SET_ENROLL_STAGES 5 175s (process:2435): libfprint-device-DEBUG: 00:01:07.462: Device reported close completion 175s (process:2435): libfprint-device-DEBUG: 00:01:07.462: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 175s (process:2435): libfprint-device-DEBUG: 00:01:07.462: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s 175s ok 175s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.462: 60383544: ../libfprint/drivers/virtual-device.c:387 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.462: 60383556: ../libfprint/drivers/virtual-device-listener.c:153 175s (process:2435): libfprint-device-DEBUG: 00:01:07.462: Device reported open completion 175s (process:2435): libfprint-device-DEBUG: 00:01:07.462: Completing action FPI_DEVICE_ACTION_OPEN in idle! 175s (process:2435): libfprint-device-DEBUG: 00:01:07.462: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.462: Got a new connection! 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.462: Got instructions of length 9 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.462: Received command SLEEP 100 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.462: Got a new connection! 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.462: Got instructions of length 7 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.462: Received command ERROR 4 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.462: Processing command SLEEP 100 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.462: Sleeping 100ms 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.562: Sleeping completed 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.562: Processing command ERROR 4 175s (process:2435): libfprint-device-DEBUG: 00:01:07.562: Device reported close completion 175s (process:2435): libfprint-device-DEBUG: 00:01:07.562: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 175s (process:2435): libfprint-device-DEBUG: 00:01:07.562: 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__.VirtualDeviceStorage.test_close_while_opening) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: 60484649: ../libfprint/drivers/virtual-device.c:387 175s (process:2435): libfprint-device-DEBUG: 00:01:07.563: Device reported open completion 175s (process:2435): libfprint-device-DEBUG: 00:01:07.563: Completing action FPI_DEVICE_ACTION_OPEN in idle! 175s (process:2435): libfprint-device-DEBUG: 00:01:07.563: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.563: Got a new connection! 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: Got instructions of length 16 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: Received command SET_KEEP_ALIVE 1 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: Keep alive toggled: 1 175s (process:2435): libfprint-device-DEBUG: 00:01:07.563: Device reported close completion 175s (process:2435): libfprint-device-DEBUG: 00:01:07.563: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 175s (process:2435): libfprint-device-DEBUG: 00:01:07.563: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 175s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:07.563: Got a new connection! 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: Got instructions of length 9 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: Received command SLEEP 500 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: 60485050: ../libfprint/drivers/virtual-device.c:387 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: Processing command SLEEP 500 175s (process:2435): libfprint-virtual_device-DEBUG: 00:01:07.563: Sleeping 500ms 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.064: Sleeping completed 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.064: 60985796: ../libfprint/drivers/virtual-device.c:387 176s (process:2435): libfprint-device-DEBUG: 00:01:08.064: Device reported open completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.064: Completing action FPI_DEVICE_ACTION_OPEN in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.064: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.064: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.064: Got instructions of length 5 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.064: Received command CONT 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.064: Processing command CONT 176s (process:2435): libfprint-device-DEBUG: 00:01:08.064: Device reported deletion completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.064: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.064: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.064: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Got instructions of length 16 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Received command SET_KEEP_ALIVE 0 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Keep alive toggled: 0 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.065: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Got instructions of length 19 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Received command SET_ENROLL_STAGES 5 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: Device reported close completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: 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 (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: 60986694: ../libfprint/drivers/virtual-device.c:387 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.065: 60986705: ../libfprint/drivers/virtual-device-listener.c:153 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: Device reported open completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: Completing action FPI_DEVICE_ACTION_OPEN in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.065: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Got instructions of length 16 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Received command IGNORED_COMMAND 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.065: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Got instructions of length 9 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Received command SLEEP 500 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Processing command IGNORED_COMMAND 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: Device reported close completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.065: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: 60987201: ../libfprint/drivers/virtual-device.c:387 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Processing command SLEEP 500 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.065: Sleeping 500ms 176s Executing: libfprint-2/virtual-device.test 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.566: Sleeping completed 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.566: 61487960: ../libfprint/drivers/virtual-device.c:387 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.566: 61487982: ../libfprint/drivers/virtual-device-listener.c:153 176s (process:2435): libfprint-device-DEBUG: 00:01:08.566: Device reported open completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.566: Completing action FPI_DEVICE_ACTION_OPEN in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.566: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.567: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Got instructions of length 5 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Received command CONT 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Processing command CONT 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Device reported deletion completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.567: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Got instructions of length 16 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Received command SET_KEEP_ALIVE 0 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Keep alive toggled: 0 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.567: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Got instructions of length 19 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Received command SET_ENROLL_STAGES 5 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Device reported close completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: 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__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: 61488961: ../libfprint/drivers/virtual-device.c:387 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.567: 61488969: ../libfprint/drivers/virtual-device-listener.c:153 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Device reported open completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Completing action FPI_DEVICE_ACTION_OPEN in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.567: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Got instructions of length 16 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Received command SET_KEEP_ALIVE 1 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Keep alive toggled: 1 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Device reported close completion 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 176s (process:2435): libfprint-device-DEBUG: 00:01:08.567: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 176s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:08.567: Got a new connection! 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Got instructions of length 9 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Received command SLEEP 500 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: 61489224: ../libfprint/drivers/virtual-device.c:387 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Processing command SLEEP 500 176s (process:2435): libfprint-virtual_device-DEBUG: 00:01:08.567: Sleeping 500ms 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.068: Sleeping completed 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.068: 61989920: ../libfprint/drivers/virtual-device.c:387 177s (process:2435): libfprint-device-DEBUG: 00:01:09.068: Device reported open completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.068: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.068: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.068: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Got instructions of length 5 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Received command CONT 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Processing command CONT 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Device reported deletion completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.069: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Got instructions of length 16 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Received command SET_KEEP_ALIVE 0 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Keep alive toggled: 0 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.069: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Got instructions of length 19 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Received command SET_ENROLL_STAGES 5 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Device reported close completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 177s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: 61990800: ../libfprint/drivers/virtual-device.c:387 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.069: 61990810: ../libfprint/drivers/virtual-device-listener.c:153 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Device reported open completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.069: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.069: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Got instructions of length 9 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Received command SLEEP 100 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.069: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Got instructions of length 7 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Received command ERROR 7 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Processing command SLEEP 100 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.069: Sleeping 100ms 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Sleeping completed 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Processing command ERROR 7 177s (process:2435): libfprint-device-DEBUG: 00:01:09.170: Device reported deletion completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.170: Completing action FPI_DEVICE_ACTION_DELETE in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.170: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.170: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Got instructions of length 5 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Received command CONT 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Processing command CONT 177s (process:2435): libfprint-device-DEBUG: 00:01:09.170: Device reported deletion completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.170: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.170: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.170: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Got instructions of length 16 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Received command SET_KEEP_ALIVE 0 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Keep alive toggled: 0 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.170: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Got instructions of length 19 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.170: Received command SET_ENROLL_STAGES 5 177s (process:2435): libfprint-device-DEBUG: 00:01:09.170: Device reported close completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.170: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 177s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: 62092536: ../libfprint/drivers/virtual-device.c:387 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.171: 62092546: ../libfprint/drivers/virtual-device-listener.c:153 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported open completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.171: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Got instructions of length 16 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Received command SCAN right-thumb 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Processing command SCAN right-thumb 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported enroll progress, reported 1 of 5 have been completed 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Sleeping completed 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.171: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Got instructions of length 16 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Received command SCAN right-thumb 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Processing command SCAN right-thumb 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported enroll progress, reported 2 of 5 have been completed 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Sleeping completed 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.171: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Got instructions of length 16 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Received command SCAN right-thumb 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Processing command SCAN right-thumb 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported enroll progress, reported 3 of 5 have been completed 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Sleeping completed 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.171: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Got instructions of length 16 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Received command SCAN right-thumb 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Processing command SCAN right-thumb 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported enroll progress, reported 4 of 5 have been completed 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Sleeping completed 177s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:09.171: Got a new connection! 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Got instructions of length 16 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Received command SCAN right-thumb 177s (process:2435): libfprint-virtual_device-DEBUG: 00:01:09.171: Processing command SCAN right-thumb 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported enroll progress, reported 5 of 5 have been completed 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported enroll completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Device reported finger status change: FP_FINGER_STATUS_NONE 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Print for finger FP_FINGER_RIGHT_THUMB enrolled 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.171: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:09.672: Deleting print right-thumb for user testuser 177s (process:2435): libfprint-device-DEBUG: 00:01:09.672: Device reported deletion completion 177s (process:2435): libfprint-device-DEBUG: 00:01:09.672: Completing action FPI_DEVICE_ACTION_DELETE in idle! 177s (process:2435): libfprint-device-DEBUG: 00:01:09.673: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:10.173: Deleting print right-thumb for user testuser 178s (process:2435): libfprint-device-DEBUG: 00:01:10.173: Device reported deletion completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.173: Completing action FPI_DEVICE_ACTION_DELETE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.173: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.174: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: Got instructions of length 5 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: Received command CONT 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: Processing command CONT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Device reported deletion completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.174: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: Got instructions of length 16 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: Received command SET_KEEP_ALIVE 0 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: Keep alive toggled: 0 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.174: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: Got instructions of length 19 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: Received command SET_ENROLL_STAGES 5 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Device reported close completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s Enroll done 178s ok 178s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.174: 63096248: ../libfprint/drivers/virtual-device.c:387 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.174: 63096258: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Device reported open completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Got instructions of length 5 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Received command CONT 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Processing command CONT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Device reported deletion completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Got instructions of length 16 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Received command SET_KEEP_ALIVE 0 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Keep alive toggled: 0 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Got instructions of length 19 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Received command SET_ENROLL_STAGES 5 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Device reported close completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s ok 178s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: 63096702: ../libfprint/drivers/virtual-device.c:387 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: 63096708: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Device reported open completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Got instructions of length 5 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Received command CONT 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Processing command CONT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Device reported deletion completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Got instructions of length 16 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Received command SET_KEEP_ALIVE 0 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Keep alive toggled: 0 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Got instructions of length 19 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Received command SET_ENROLL_STAGES 5 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Device reported close completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s ok 178s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: 63097072: ../libfprint/drivers/virtual-device.c:387 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: 63097079: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Device reported open completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.175: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Got instructions of length 10 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.175: Received command SLEEP 1500 178s (process:2435): libfprint-device-DEBUG: 00:01:10.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.176: Processing command SLEEP 1500 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.176: Sleeping 1500ms 178s (process:2435): libfprint-device-DEBUG: 00:01:10.476: Idle cancelling on ongoing operation! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.476: Got cancellation! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-device-DEBUG: 00:01:10.476: Device reported identify completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.476: Device reported finger status change: FP_FINGER_STATUS_NONE 178s (process:2435): libfprint-device-DEBUG: 00:01:10.476: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.476: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.676: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: Got instructions of length 5 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: Received command CONT 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: Processing command CONT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.676: Device reported deletion completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.676: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.676: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.676: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: Got instructions of length 16 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: Received command SET_KEEP_ALIVE 0 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: Keep alive toggled: 0 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.676: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: Got instructions of length 19 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: Received command SET_ENROLL_STAGES 5 178s (process:2435): libfprint-device-DEBUG: 00:01:10.676: Device reported close completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.676: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.676: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s ok 178s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.676: 63598351: ../libfprint/drivers/virtual-device.c:387 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.676: 63598363: ../libfprint/drivers/virtual-device-listener.c:153 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported open completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.677: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Got instructions of length 14 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Received command SCAN foo-print 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Processing command SCAN foo-print 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported enroll progress, reported 1 of 5 have been completed 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Sleeping completed 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.677: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Got instructions of length 14 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Received command SCAN foo-print 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Processing command SCAN foo-print 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported enroll progress, reported 2 of 5 have been completed 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Sleeping completed 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.677: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Got instructions of length 14 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Received command SCAN foo-print 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Processing command SCAN foo-print 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported enroll progress, reported 3 of 5 have been completed 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Sleeping completed 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.677: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Got instructions of length 14 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Received command SCAN foo-print 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Processing command SCAN foo-print 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported enroll progress, reported 4 of 5 have been completed 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Sleeping completed 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.677: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Got instructions of length 14 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Received command SCAN foo-print 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Processing command SCAN foo-print 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported enroll progress, reported 5 of 5 have been completed 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported enroll completion 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Device reported finger status change: FP_FINGER_STATUS_NONE 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Print for finger FP_FINGER_LEFT_RING enrolled 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.677: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Got instructions of length 9 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Received command SLEEP 100 178s (process:2435): libfprint-device-DEBUG: 00:01:10.677: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Processing command SLEEP 100 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.677: Sleeping 100ms 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.678: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.678: Got instructions of length 14 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.678: Received command SCAN bar-print 178s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:10.678: Got a new connection! 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.678: Got instructions of length 9 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.678: Received command SLEEP 800 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.778: Sleeping completed 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.778: Processing command SCAN bar-print 178s (process:2435): libfprint-device-DEBUG: 00:01:10.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-device-DEBUG: 00:01:10.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 178s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:10.778: Trying to identify print 'bar-print' against a gallery of 1 prints 178s (process:2435): libfprint-device-DEBUG: 00:01:10.778: Device reported identify result 178s (process:2435): libfprint-device-DEBUG: 00:01:10.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.778: Processing command SLEEP 800 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.778: Sleeping 800ms 178s (process:2435): libfprint-virtual_device-DEBUG: 00:01:10.778: Sleeping now, command queued for later: SCAN bar-print 179s (process:2435): libfprint-device-DEBUG: 00:01:11.015: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.578: Sleeping completed 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.578: Processing command SCAN bar-print 179s (process:2435): libfprint-device-DEBUG: 00:01:11.578: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 179s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:11.578: Trying to identify print 'bar-print' against a gallery of 1 prints 179s (process:2435): libfprint-device-DEBUG: 00:01:11.578: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:2435): libfprint-device-DEBUG: 00:01:11.578: Device reported identify completion 179s (process:2435): libfprint-device-DEBUG: 00:01:11.578: Device reported finger status change: FP_FINGER_STATUS_NONE 179s (process:2435): libfprint-device-DEBUG: 00:01:11.578: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 179s (process:2435): libfprint-device-DEBUG: 00:01:11.578: Updated temperature model after 0.56 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:11.579: Got a new connection! 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Got instructions of length 5 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Received command CONT 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Processing command CONT 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Device reported deletion completion 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:11.579: Got a new connection! 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Got instructions of length 16 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Received command SET_KEEP_ALIVE 0 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Keep alive toggled: 0 179s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:11.579: Got a new connection! 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Got instructions of length 19 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Received command SET_ENROLL_STAGES 5 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Device reported close completion 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s Enroll done 179s ok 179s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: 64501001: ../libfprint/drivers/virtual-device.c:387 179s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:11.579: 64501007: ../libfprint/drivers/virtual-device-listener.c:153 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Device reported open completion 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:11.579: Got a new connection! 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Got instructions of length 26 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Received command SET_CANCELLATION_ENABLED 0 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Cancellation support toggled: 0 179s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:11.579: Got a new connection! 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Got instructions of length 10 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Received command SLEEP 1500 179s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:11.579: Got a new connection! 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Got instructions of length 14 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Received command SCAN foo-print 179s (process:2435): libfprint-device-DEBUG: 00:01:11.579: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Processing command SLEEP 1500 179s (process:2435): libfprint-virtual_device-DEBUG: 00:01:11.579: Sleeping 1500ms 179s (process:2435): libfprint-device-DEBUG: 00:01:11.880: Idle cancelling on ongoing operation! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.080: Sleeping completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.081: Processing command SCAN foo-print 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.081: 66003188: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.081: 66003200: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.081: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.082: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.082: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.082: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.082: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.082: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Print for finger FP_FINGER_LEFT_LITTLE enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.082: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.082: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.082: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.082: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s Enroll done 181s Enroll done 181s ok 181s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: 66004645: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: 66004654: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Print for finger FP_FINGER_LEFT_LITTLE enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.083: Got a new connection! 181s Executing: libfprint-2/virtual-device.test 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.083: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.084: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.084: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.084: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s Enroll done 181s ok 181s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: 66005589: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: 66005596: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.084: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.084: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.084: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SET_ENROLL_STAGES 8 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command RETRY 1 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command RETRY 3 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command RETRY 2 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SLEEP 10 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command SLEEP 20 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command RETRY 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.084: Received command RETRY 3 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.084: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.085: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Received command SCAN another-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.085: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.085: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Received command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported enroll progress, reported 1 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported enroll progress, reported 2 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported enroll progress, reported 2 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported enroll progress, reported 3 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command RETRY 3 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported enroll progress, reported 3 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported enroll progress, reported 4 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command RETRY 2 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported enroll progress, reported 4 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.085: Device reported enroll progress, reported 5 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Processing command SLEEP 10 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.085: Sleeping 10ms 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.095: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.095: Processing command SLEEP 20 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.095: Sleeping 20ms 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Processing command RETRY 0 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported enroll progress, reported 5 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Processing command RETRY 3 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported enroll progress, reported 5 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported enroll progress, reported 6 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Processing command SCAN another-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported enroll progress, reported 6 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported enroll progress, reported 7 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.115: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported enroll progress, reported 8 of 8 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Print for finger FP_FINGER_UNKNOWN enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.115: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: 66037733: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: 66037743: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SLEEP 50 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command RETRY 1 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SLEEP 50 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command RETRY 2 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SCAN another-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.116: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Received command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.116: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Processing command SLEEP 50 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.116: Sleeping 50ms 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Processing command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.167: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Processing command SLEEP 50 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.167: Sleeping 50ms 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.217: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.217: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.217: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.217: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.217: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Processing command RETRY 2 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Processing command SCAN another-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Print for finger FP_FINGER_UNKNOWN enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.218: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.218: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.218: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.218: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.218: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: 66140451: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.219: 66140465: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.219: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.219: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.219: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.219: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.219: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Print for finger FP_FINGER_LEFT_RING enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.219: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.219: Received command ERROR 0 181s (process:2435): libfprint-device-DEBUG: 00:01:13.219: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Processing command ERROR 0 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s Enroll done 181s ok 181s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: 66141818: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: 66141826: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.220: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.220: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.220: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Print for finger FP_FINGER_LEFT_THUMB enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.221: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:13.221: Trying to identify print 'testprint' against a gallery of 1 prints 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported identify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.221: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.221: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.221: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s Enroll done 181s ok 181s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: 66143005: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.221: 66143012: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.221: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.221: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.221: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.221: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.221: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.222: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.222: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Print for finger FP_FINGER_LEFT_RING enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.222: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Got instructions of length 18 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Received command SCAN not-testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Processing command SCAN not-testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:13.222: Trying to identify print 'not-testprint' against a gallery of 1 prints 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported identify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.222: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.222: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.222: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s Enroll done 181s ok 181s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: 66144173: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.222: 66144181: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.222: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Received command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Processing command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.222: Virtual device scan failed with error: The swipe was too short, please try again. 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported verify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported verify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.222: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: 66144720: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: 66144728: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.223: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SET_ENROLL_STAGES 8 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command RETRY 1 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command RETRY 3 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command RETRY 2 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Received command SLEEP 10 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.223: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.223: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Received command SLEEP 20 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.224: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Received command RETRY 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.224: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Received command RETRY 3 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.224: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.224: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Received command SCAN another-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.224: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Received command SCAN print-id 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.224: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Received command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported enroll progress, reported 1 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported enroll progress, reported 2 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported enroll progress, reported 2 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported enroll progress, reported 3 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command RETRY 3 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported enroll progress, reported 3 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported enroll progress, reported 4 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command RETRY 2 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported enroll progress, reported 4 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.224: Device reported enroll progress, reported 5 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Processing command SLEEP 10 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.224: Sleeping 10ms 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.234: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.234: Processing command SLEEP 20 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.234: Sleeping 20ms 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Processing command RETRY 0 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported enroll progress, reported 5 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Processing command RETRY 3 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported enroll progress, reported 5 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported enroll progress, reported 6 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Processing command SCAN another-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported enroll progress, reported 6 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported enroll progress, reported 7 of 8 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.254: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.254: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Device reported enroll progress, reported 8 of 8 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Print for finger FP_FINGER_UNKNOWN enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.255: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Received command RETRY 2 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Processing command RETRY 2 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Virtual device scan failed with error: The finger was not centered properly, please try again. 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Device reported verify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Device reported verify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.255: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Received command SLEEP 50 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.255: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Received command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.255: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Processing command SLEEP 50 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.255: Sleeping 50ms 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.305: Sleeping completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.305: Processing command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.305: Virtual device scan failed with error: The swipe was too short, please try again. 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported verify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported verify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.305: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.305: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.305: Received command SCAN another-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.305: Processing command SCAN another-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.305: Virtual device scanned print another-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported verify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported verify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.305: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.306: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Got instructions of length 13 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Received command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Processing command SCAN print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Virtual device scanned print print-id 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported verify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported verify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.306: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.306: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.306: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: 66227967: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.306: 66227976: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.306: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.306: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.306: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.306: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.306: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Received command RETRY 1 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Processing command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Print for finger FP_FINGER_LEFT_LITTLE enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s Enroll done 181s ok 181s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: 66229175: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: 66229182: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Received command FINGER 1 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.307: Processing command FINGER 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.307: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Received command FINGER 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Processing command FINGER 0 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Idle cancelling on ongoing operation! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Got cancellation! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.308: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.308: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.308: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: 66229798: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.308: 66229805: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.308: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Received command SLEEP 10 181s (process:2435): libfprint-device-DEBUG: 00:01:13.308: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Processing command SLEEP 10 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.308: Sleeping 10ms 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Sleeping completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.318: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Received command FINGER 1 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Processing command FINGER 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.318: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Got instructions of length 8 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Received command FINGER 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Processing command FINGER 0 181s (process:2435): libfprint-device-DEBUG: 00:01:13.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.318: Idle cancelling on ongoing operation! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Got cancellation! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.318: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.318: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.318: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.318: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.318: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.318: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: 66240625: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: 66240637: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Received command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Received command SCAN right-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Received command SCAN right-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Received command SCAN right-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Received command SCAN right-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Print for finger FP_FINGER_RIGHT_THUMB enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.319: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.319: Received command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.319: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.320: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Received command SCAN left-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.320: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Received command SCAN left-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.320: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Received command SCAN left-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.320: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Received command SCAN left-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Print for finger FP_FINGER_LEFT_THUMB enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.320: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Received command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:13.320: Trying to identify print 'right-thumb' against a gallery of 2 prints 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported identify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.320: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Received command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:13.320: Trying to identify print 'left-thumb' against a gallery of 2 prints 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported identify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.320: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.320: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.320: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.320: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s Enroll done 181s Enroll done 181s ok 181s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: 66242568: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: 66242576: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Got instructions of length 23 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Received command SCAN not-existing-print 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Processing command SCAN not-existing-print 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:13.321: Trying to identify print 'not-existing-print' against a gallery of 1 prints 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported identify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: 66243086: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: 66243095: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Received command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.321: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Received command SCAN right-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.321: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.321: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.322: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Received command SCAN right-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.322: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Received command SCAN right-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.322: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Received command SCAN right-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Print for finger FP_FINGER_RIGHT_THUMB enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.322: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Received command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.322: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Received command SCAN left-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.322: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Received command SCAN left-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.322: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Received command SCAN left-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.322: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Received command SCAN left-thumb 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.322: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Print for finger FP_FINGER_LEFT_THUMB enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.322: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Received command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Processing command SCAN right-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:13.323: Trying to identify print 'right-thumb' against a gallery of 1 prints 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported identify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Got instructions of length 15 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Received command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Processing command SCAN left-thumb 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:13.323: Trying to identify print 'left-thumb' against a gallery of 1 prints 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported identify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s Enroll done 181s Enroll done 181s ok 181s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: 66245029: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: 66245036: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Got instructions of length 7 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Received command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Processing command RETRY 1 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported identify result 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported identify completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.323: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.323: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s ok 181s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: 66245553: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: 66245562: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s skipped 'Device supports identification' 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Got instructions of length 5 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command CONT 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Processing command CONT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported deletion completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Got instructions of length 16 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command SET_KEEP_ALIVE 0 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Keep alive toggled: 0 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Got instructions of length 19 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command SET_ENROLL_STAGES 5 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported close completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: 66245925: ../libfprint/drivers/virtual-device.c:387 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: 66245932: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported open completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported enroll progress, reported 1 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported enroll progress, reported 2 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported enroll progress, reported 3 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.324: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.324: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.324: Device reported enroll progress, reported 4 of 5 have been completed 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.325: Sleeping completed 181s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:13.325: Got a new connection! 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.325: Got instructions of length 14 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.325: Received command SCAN testprint 181s (process:2435): libfprint-virtual_device-DEBUG: 00:01:13.325: Processing command SCAN testprint 181s (process:2435): libfprint-device-DEBUG: 00:01:13.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:2435): libfprint-device-DEBUG: 00:01:13.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:2435): libfprint-device-DEBUG: 00:01:13.325: Device reported enroll progress, reported 5 of 5 have been completed 181s (process:2435): libfprint-device-DEBUG: 00:01:13.325: Device reported enroll completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.325: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:2435): libfprint-device-DEBUG: 00:01:13.325: Print for finger FP_FINGER_RIGHT_THUMB enrolled 181s (process:2435): libfprint-device-DEBUG: 00:01:13.325: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 181s (process:2435): libfprint-device-DEBUG: 00:01:13.825: Device reported listing completion 181s (process:2435): libfprint-device-DEBUG: 00:01:13.826: Completing action FPI_DEVICE_ACTION_LIST in idle! 181s (process:2435): libfprint-device-DEBUG: 00:01:13.826: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:14.326: Deleting print testprint for user testuser 182s (process:2435): libfprint-device-DEBUG: 00:01:14.327: Device reported deletion completion 182s (process:2435): libfprint-device-DEBUG: 00:01:14.327: Completing action FPI_DEVICE_ACTION_DELETE in idle! 182s (process:2435): libfprint-device-DEBUG: 00:01:14.327: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s (process:2435): libfprint-device-DEBUG: 00:01:14.827: Device reported listing completion 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Completing action FPI_DEVICE_ACTION_LIST in idle! 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.828: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: Got instructions of length 5 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: Received command CONT 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: Processing command CONT 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Device reported deletion completion 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.828: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: Got instructions of length 16 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: Received command SET_KEEP_ALIVE 0 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: Keep alive toggled: 0 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.828: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: Got instructions of length 19 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: Received command SET_ENROLL_STAGES 5 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Device reported close completion 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s Enroll done 182s 182s blub 'testprint' 182s ok 182s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.828: 67750297: ../libfprint/drivers/virtual-device.c:387 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.828: 67750308: ../libfprint/drivers/virtual-device-listener.c:153 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Device reported open completion 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Completing action FPI_DEVICE_ACTION_OPEN in idle! 182s (process:2435): libfprint-device-DEBUG: 00:01:14.828: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.829: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Got instructions of length 14 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Received command SCAN testprint 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Processing command SCAN testprint 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported enroll progress, reported 1 of 5 have been completed 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Sleeping completed 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.829: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Got instructions of length 14 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Received command SCAN testprint 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Processing command SCAN testprint 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported enroll progress, reported 2 of 5 have been completed 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Sleeping completed 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.829: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Got instructions of length 14 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Received command SCAN testprint 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Processing command SCAN testprint 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported enroll progress, reported 3 of 5 have been completed 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Sleeping completed 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.829: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Got instructions of length 14 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Received command SCAN testprint 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Processing command SCAN testprint 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported enroll progress, reported 4 of 5 have been completed 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Sleeping completed 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.829: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Got instructions of length 14 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Received command SCAN testprint 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Processing command SCAN testprint 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported enroll progress, reported 5 of 5 have been completed 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported enroll completion 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Device reported finger status change: FP_FINGER_STATUS_NONE 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Print for finger FP_FINGER_RIGHT_THUMB enrolled 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 182s (process:2435): libfprint-device-DEBUG: 00:01:14.829: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:14.829: Got a new connection! 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Got instructions of length 16 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Received command REMOVE testprint 182s (process:2435): libfprint-virtual_device-DEBUG: 00:01:14.829: Processing command REMOVE testprint 183s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:15.330: Deleting print testprint for user testuser 183s (process:2435): libfprint-device-DEBUG: 00:01:15.330: Device reported deletion completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.330: Completing action FPI_DEVICE_ACTION_DELETE in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.330: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.331: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: Got instructions of length 5 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: Received command CONT 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: Processing command CONT 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Device reported deletion completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.331: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: Got instructions of length 16 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: Received command SET_KEEP_ALIVE 0 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: Keep alive toggled: 0 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.331: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: Got instructions of length 19 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: Received command SET_ENROLL_STAGES 5 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Device reported close completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s Enroll done 183s ok 183s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.331: 68252904: ../libfprint/drivers/virtual-device.c:387 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.331: 68252917: ../libfprint/drivers/virtual-device-listener.c:153 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Device reported open completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Completing action FPI_DEVICE_ACTION_OPEN in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.331: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-device-DEBUG: 00:01:15.832: Device reported listing completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.832: Completing action FPI_DEVICE_ACTION_LIST in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.832: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.832: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.832: Got instructions of length 5 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.832: Received command CONT 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.832: Processing command CONT 183s (process:2435): libfprint-device-DEBUG: 00:01:15.832: Device reported deletion completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.832: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.832: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.832: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.832: Got instructions of length 16 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.832: Received command SET_KEEP_ALIVE 0 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.832: Keep alive toggled: 0 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.832: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: Got instructions of length 19 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: Received command SET_ENROLL_STAGES 5 183s (process:2435): libfprint-device-DEBUG: 00:01:15.833: Device reported close completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.833: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.833: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s ok 183s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: 68754645: ../libfprint/drivers/virtual-device.c:387 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.833: 68754658: ../libfprint/drivers/virtual-device-listener.c:153 183s (process:2435): libfprint-device-DEBUG: 00:01:15.833: Device reported open completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.833: Completing action FPI_DEVICE_ACTION_OPEN in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.833: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.833: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: Got instructions of length 9 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: Received command SLEEP 100 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.833: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: Got instructions of length 7 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: Received command ERROR 4 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: Processing command SLEEP 100 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.833: Sleeping 100ms 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.933: Sleeping completed 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Processing command ERROR 4 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Device reported listing completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Completing action FPI_DEVICE_ACTION_LIST in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.934: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Got instructions of length 5 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Received command CONT 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Processing command CONT 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Device reported deletion completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.934: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Got instructions of length 16 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Received command SET_KEEP_ALIVE 0 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Keep alive toggled: 0 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.934: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Got instructions of length 19 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: Received command SET_ENROLL_STAGES 5 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Device reported close completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.934: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s ok 183s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.934: 68856344: ../libfprint/drivers/virtual-device.c:387 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.934: 68856356: ../libfprint/drivers/virtual-device-listener.c:153 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported open completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Completing action FPI_DEVICE_ACTION_OPEN in idle! 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.935: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Got instructions of length 9 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Received command INSERT p1 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.935: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Got instructions of length 7 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Received command SCAN p2 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Processing command INSERT p1 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Processing command SCAN p2 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported enroll progress, reported 1 of 5 have been completed 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Sleeping completed 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.935: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Got instructions of length 7 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Received command SCAN p2 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Processing command SCAN p2 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported enroll progress, reported 2 of 5 have been completed 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Sleeping completed 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.935: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Got instructions of length 7 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Received command SCAN p2 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Processing command SCAN p2 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported enroll progress, reported 3 of 5 have been completed 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Sleeping completed 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.935: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Got instructions of length 7 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Received command SCAN p2 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Processing command SCAN p2 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported enroll progress, reported 4 of 5 have been completed 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Sleeping completed 183s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:15.935: Got a new connection! 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Got instructions of length 7 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Received command SCAN p2 183s (process:2435): libfprint-virtual_device-DEBUG: 00:01:15.935: Processing command SCAN p2 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported enroll progress, reported 5 of 5 have been completed 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported enroll completion 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Device reported finger status change: FP_FINGER_STATUS_NONE 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Print for finger FP_FINGER_LEFT_LITTLE enrolled 183s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:15.935: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-device-DEBUG: 00:01:16.436: Device reported listing completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.436: Completing action FPI_DEVICE_ACTION_LIST in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.436: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.437: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Got instructions of length 5 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Received command CONT 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Processing command CONT 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Device reported deletion completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.437: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Got instructions of length 16 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Received command SET_KEEP_ALIVE 0 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Keep alive toggled: 0 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.437: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Got instructions of length 19 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Received command SET_ENROLL_STAGES 5 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Device reported close completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s Enroll done 184s ok 184s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: 69358988: ../libfprint/drivers/virtual-device.c:387 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.437: 69359019: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Device reported open completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.437: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Got instructions of length 16 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Received command IGNORED_COMMAND 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.437: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Got instructions of length 7 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Received command ERROR 5 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.437: Processing command IGNORED_COMMAND 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Device reported close completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.437: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: 69359476: ../libfprint/drivers/virtual-device.c:387 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Processing command ERROR 5 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported open completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s ok 184s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: 69359577: ../libfprint/drivers/virtual-device.c:387 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.438: 69359585: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported open completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.438: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Got instructions of length 16 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Received command SET_KEEP_ALIVE 1 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Keep alive toggled: 1 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported close completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.438: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Got instructions of length 7 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Received command ERROR 5 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: 69359819: ../libfprint/drivers/virtual-device.c:387 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Processing command ERROR 5 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported open completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s ok 184s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: 69359906: ../libfprint/drivers/virtual-device.c:387 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported open completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.438: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Got instructions of length 19 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Received command SET_ENROLL_STAGES 1 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.438: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Got instructions of length 14 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Received command SCAN testprint 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Processing command SCAN testprint 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported enroll progress, reported 1 of 1 have been completed 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported enroll completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Print for finger FP_FINGER_LEFT_LITTLE enrolled 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.438: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Got instructions of length 5 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Received command CONT 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.438: Processing command CONT 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Device reported deletion completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.438: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.439: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Got instructions of length 16 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Received command SET_KEEP_ALIVE 0 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Keep alive toggled: 0 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.439: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Got instructions of length 19 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Received command SET_ENROLL_STAGES 5 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported close completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s Enroll done 184s ok 184s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: 69360598: ../libfprint/drivers/virtual-device.c:387 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.439: 69360607: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported open completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.439: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Got instructions of length 23 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Received command SCAN not-existing-print 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Processing command SCAN not-existing-print 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Virtual device scanned print not-existing-print 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported verify result 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported verify completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.439: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Got instructions of length 5 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Received command CONT 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Processing command CONT 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported deletion completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.439: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Got instructions of length 16 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Received command SET_KEEP_ALIVE 0 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Keep alive toggled: 0 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.439: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Got instructions of length 19 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: Received command SET_ENROLL_STAGES 5 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Device reported close completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.439: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s ok 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.439: 69361246: ../libfprint/drivers/virtual-device.c:752 184s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:2435): libfprint-context-DEBUG: 00:01:16.440: Initializing FpContext (libfprint version 1.94.8+tod1) 184s (process:2435): libfprint-tod-DEBUG: 00:01:16.440: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 184s (process:2435): libfprint-context-DEBUG: 00:01:16.440: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-kh5tda04/virtual-device.socket 184s (process:2435): libfprint-context-DEBUG: 00:01:16.440: created 184s (process:2435): libfprint-context-DEBUG: 00:01:16.440: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ybujci0r/virtual-device-storage.socket 184s (process:2435): libfprint-context-DEBUG: 00:01:16.440: created 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Device reported probe completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Device reported probe completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Completing action FPI_DEVICE_ACTION_PROBE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Completing action FPI_DEVICE_ACTION_PROBE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.440: 69362004: ../libfprint/drivers/virtual-device.c:387 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.440: 69362014: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Device reported open completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.440: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.440: Got instructions of length 7 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.440: Received command UNPLUG 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Device reported close completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.441: 69362413: ../libfprint/drivers/virtual-device.c:752 184s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:16.441: 69362427: ../libfprint/drivers/virtual-device-storage.c:253 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.441: 69362434: ../libfprint/drivers/virtual-device.c:752 184s ok 184s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:2435): libfprint-context-DEBUG: 00:01:16.441: Initializing FpContext (libfprint version 1.94.8+tod1) 184s (process:2435): libfprint-tod-DEBUG: 00:01:16.441: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 184s (process:2435): libfprint-context-DEBUG: 00:01:16.441: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-kh5tda04/virtual-device.socket 184s (process:2435): libfprint-context-DEBUG: 00:01:16.441: created 184s (process:2435): libfprint-context-DEBUG: 00:01:16.441: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ybujci0r/virtual-device-storage.socket 184s (process:2435): libfprint-context-DEBUG: 00:01:16.441: created 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Device reported probe completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Device reported probe completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Completing action FPI_DEVICE_ACTION_PROBE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Completing action FPI_DEVICE_ACTION_PROBE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.441: 69362801: ../libfprint/drivers/virtual-device.c:387 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.441: 69362808: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Device reported open completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 184s (process:2435): libfprint-device-DEBUG: 00:01:16.441: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:2435): libfprint-virtual_device_connection-DEBUG: 00:01:16.441: Got a new connection! 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.441: Got instructions of length 7 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.441: Received command UNPLUG 184s (process:2435): libfprint-device-DEBUG: 00:01:16.541: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-device-DEBUG: 00:01:16.942: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 184s (process:2435): libfprint-device-DEBUG: 00:01:16.942: Device reported verify completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.942: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:2435): libfprint-device-DEBUG: 00:01:16.942: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.942: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-device-DEBUG: 00:01:16.942: Device reported close completion 184s (process:2435): libfprint-device-DEBUG: 00:01:16.942: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:2435): libfprint-device-DEBUG: 00:01:16.942: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.942: 69864180: ../libfprint/drivers/virtual-device.c:752 184s (process:2435): libfprint-virtual_device_storage-DEBUG: 00:01:16.942: 69864199: ../libfprint/drivers/virtual-device-storage.c:253 184s (process:2435): libfprint-virtual_device-DEBUG: 00:01:16.942: 69864209: ../libfprint/drivers/virtual-device.c:752 184s ok 184s 184s ---------------------------------------------------------------------- 184s Ran 86 tests in 17.461s 184s 184s OK (skipped=1) 184s PASS: libfprint-2/virtual-device.test 184s Running test: libfprint-2/driver-egismoc-0586.test 185s ** (umockdev-run:2453): DEBUG: 00:01:16.983: umockdev.vala:127: Created udev test bed /tmp/umockdev.SZKJ22 185s ** (umockdev-run:2453): DEBUG: 00:01:16.983: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 185s ** (umockdev-run:2453): DEBUG: 00:01:16.985: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 185s ** (umockdev-run:2453): DEBUG: 00:01:16.986: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.SZKJ22/dev/bus/usb/001/021 185s ** (umockdev-run:2453): DEBUG: 00:01:16.986: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 185s ** (umockdev-run:2453): DEBUG: 00:01:16.987: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 185s ** (umockdev-run:2453): DEBUG: 00:01:16.988: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.SZKJ22/dev/bus/usb/001/001 185s ** (umockdev-run:2453): DEBUG: 00:01:16.988: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 185s ** (umockdev-run:2453): DEBUG: 00:01:16.988: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 185s (process:2457): libfprint-context-DEBUG: 00:01:17.045: Initializing FpContext (libfprint version 1.94.8+tod1) 185s (process:2457): libfprint-tod-DEBUG: 00:01:17.045: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.046: 69968334: ../libfprint/drivers/egismoc/egismoc.c:1597 185s (process:2457): libfprint-context-DEBUG: 00:01:17.047: No driver found for USB device 1D6B:0002 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.047: egismoc_probe enter --> 185s (process:2457): libfprint-device-DEBUG: 00:01:17.048: Device reported probe completion 185s (process:2457): libfprint-device-DEBUG: 00:01:17.048: Completing action FPI_DEVICE_ACTION_PROBE in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.048: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.048: Opening device 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.049: [egismoc] DEV_INIT_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.049: [egismoc] DEV_INIT_STATES entering state 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.049: [egismoc] DEV_INIT_STATES entering state 2 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.050: [egismoc] DEV_INIT_STATES entering state 3 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.050: [egismoc] DEV_INIT_STATES entering state 4 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.050: [egismoc] DEV_INIT_STATES entering state 5 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.050: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.050: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.050: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.050: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.051: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.051: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.051: Firmware version callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.051: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.051: Device firmware version is 9050.6.2.56 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.051: [egismoc] DEV_INIT_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.051: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.051: Device reported open completion 185s (process:2457): libfprint-device-DEBUG: 00:01:17.051: Completing action FPI_DEVICE_ACTION_OPEN in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.051: List 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.051: [egismoc] LIST_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.051: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.051: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.051: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.051: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.052: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.052: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.052: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.052: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.052: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.052: [egismoc] LIST_STATES entering state 1 185s (process:2457): libfprint-device-DEBUG: 00:01:17.052: Device reported listing completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.052: [egismoc] LIST_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.052: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.052: Completing action FPI_DEVICE_ACTION_LIST in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.052: Clear storage 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.052: [egismoc] DELETE_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.052: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.052: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.052: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.052: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.053: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.053: [egismoc] DELETE_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Get delete command 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.053: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.053: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.053: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Delete callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Response prefix valid: yes 185s (process:2457): libfprint-device-DEBUG: 00:01:17.053: Device reported deletion completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.053: [egismoc] DELETE_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.053: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.053: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: List 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.053: [egismoc] LIST_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.053: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.053: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.054: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.054: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.054: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.054: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.054: Number of currently enrolled fingerprints on the device is 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.054: [egismoc] LIST_STATES entering state 1 185s (process:2457): libfprint-device-DEBUG: 00:01:17.054: Device reported listing completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.054: [egismoc] LIST_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.054: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.054: Completing action FPI_DEVICE_ACTION_LIST in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.054: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2457): libfprint-device-DEBUG: 00:01:17.054: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.054: Enroll 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.054: [egismoc] ENROLL_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.055: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.055: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.055: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.055: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.055: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.055: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.055: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.055: Number of currently enrolled fingerprints on the device is 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.055: [egismoc] ENROLL_STATES entering state 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.055: [egismoc] ENROLL_STATES entering state 2 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.055: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.055: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.055: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.055: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.056: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.056: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.056: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.056: [egismoc] ENROLL_STATES entering state 3 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.056: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.056: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.056: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.056: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.056: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.056: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.056: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.056: [egismoc] ENROLL_STATES entering state 4 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.056: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.056: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.056: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.057: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.057: [egismoc] ENROLL_STATES entering state 5 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.057: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.057: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.057: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.057: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.057: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.057: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.057: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.057: [egismoc] ENROLL_STATES entering state 6 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.057: Get check command 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.057: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.057: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.057: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.057: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.058: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Enroll check callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Response suffix valid: yes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.058: [egismoc] ENROLL_STATES entering state 7 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.058: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.058: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.058: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.058: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.058: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.058: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.058: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.059: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.059: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.059: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.059: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.059: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.059: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.059: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.059: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.059: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.059: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.059: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.059: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.059: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.059: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.059: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.060: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.060: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.060: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.060: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Partial capture successful. Please touch the sensor again (1/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.060: Device reported enroll progress, reported 1 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.060: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.060: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.060: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.060: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.061: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.061: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.061: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.061: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.061: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.061: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.061: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.061: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.061: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.061: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.061: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.061: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.061: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.061: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.062: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.062: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.062: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.062: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.062: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Partial capture successful. Please touch the sensor again (2/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.062: Device reported enroll progress, reported 2 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.062: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.062: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.062: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.062: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.063: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.063: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.063: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.063: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.063: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.063: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.063: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.063: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.063: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.063: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.064: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.064: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.064: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.064: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.064: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.064: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.064: Partial capture successful. Please touch the sensor again (3/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.064: Device reported enroll progress, reported 3 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.064: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.064: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.064: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.064: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.064: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.064: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.064: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.065: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.065: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.065: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.065: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.065: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.065: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.065: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.065: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.065: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Partial capture successful. Please touch the sensor again (4/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.066: Device reported enroll progress, reported 4 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.066: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.066: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.067: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.067: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.067: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.067: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.067: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.067: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.067: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Partial capture successful. Please touch the sensor again (5/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.067: Device reported enroll progress, reported 5 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.067: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.067: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.067: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.068: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.068: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.068: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.068: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.068: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.068: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.068: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.068: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.068: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.068: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.068: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.068: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.068: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.068: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.069: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.069: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.069: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.069: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.069: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Partial capture successful. Please touch the sensor again (6/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.069: Device reported enroll progress, reported 6 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.069: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.069: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.069: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.069: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.070: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.070: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.070: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.070: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.070: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.070: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.070: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.070: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.070: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.070: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.071: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.071: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Partial capture successful. Please touch the sensor again (7/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.071: Device reported enroll progress, reported 7 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.071: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.071: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.071: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.071: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.071: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.071: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.072: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.072: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.072: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.072: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.072: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.072: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.072: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.072: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.072: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.072: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.072: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.072: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.072: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.072: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.072: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.072: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.072: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.073: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Response suffix valid: NO 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Response suffix valid: yes 185s (process:2457): libfprint-device-DEBUG: 00:01:17.073: Device reported enroll progress, reported 7 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.073: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.073: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.073: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.073: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.073: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.073: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.073: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.073: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.074: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.074: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.074: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.074: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.074: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.074: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.074: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.074: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.074: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.074: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.074: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.074: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.075: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Partial capture successful. Please touch the sensor again (8/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.075: Device reported enroll progress, reported 8 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.075: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.075: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.075: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.075: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.075: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.075: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.075: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.075: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.076: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.076: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.076: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.076: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.076: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.076: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.076: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Response suffix valid: NO 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Response suffix valid: yes 185s (process:2457): libfprint-device-DEBUG: 00:01:17.076: Device reported enroll progress, reported 8 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.076: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.076: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.076: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.077: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.077: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.077: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.077: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.078: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.078: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Partial capture successful. Please touch the sensor again (9/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.078: Device reported enroll progress, reported 9 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.078: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.078: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.078: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.078: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.078: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.078: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.078: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.079: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.079: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.079: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.079: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.079: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.079: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.079: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.079: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.079: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.079: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.079: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.079: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.079: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.079: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.080: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Partial capture successful. Please touch the sensor again (10/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.080: Device reported enroll progress, reported 10 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.080: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.080: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.080: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.080: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.080: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.080: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.080: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.080: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.081: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.081: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.081: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.081: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.081: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.081: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.081: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Partial capture successful. Please touch the sensor again (11/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.081: Device reported enroll progress, reported 11 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.081: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.081: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.081: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.082: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.082: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.082: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.082: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.082: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.082: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.082: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.082: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.082: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.082: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.082: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.082: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.082: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.082: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.083: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.083: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.083: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.083: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.083: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Partial capture successful. Please touch the sensor again (12/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.083: Device reported enroll progress, reported 12 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.083: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.083: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.083: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.083: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.084: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.084: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.084: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.084: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.084: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.084: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.084: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.084: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.084: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.084: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.084: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.085: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.085: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.085: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.085: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.085: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.085: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.085: Partial capture successful. Please touch the sensor again (13/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.085: Device reported enroll progress, reported 13 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.085: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.085: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.085: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.085: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.085: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.085: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.085: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.086: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.086: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.086: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.086: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.086: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.086: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.086: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.086: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.086: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.087: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.087: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Partial capture successful. Please touch the sensor again (14/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.087: Device reported enroll progress, reported 14 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.087: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.087: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.087: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.087: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.087: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.087: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.087: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.088: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.088: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.088: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.088: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.088: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.088: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.088: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.088: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.088: Partial capture successful. Please touch the sensor again (15/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.088: Device reported enroll progress, reported 15 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.089: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.089: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.089: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.089: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.089: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.089: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.089: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.089: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.089: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.089: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.089: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.089: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.089: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.090: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.090: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.090: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.090: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.090: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.090: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.090: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Partial capture successful. Please touch the sensor again (16/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.090: Device reported enroll progress, reported 16 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.090: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.090: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.090: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.091: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.091: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.091: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.091: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.091: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.091: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.091: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.091: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.091: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.091: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.091: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.091: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.091: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.091: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.091: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.092: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.092: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.092: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.092: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.092: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Partial capture successful. Please touch the sensor again (17/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.092: Device reported enroll progress, reported 17 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.092: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.092: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.092: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.092: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.093: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.093: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.093: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.093: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.093: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.093: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.093: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.093: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.093: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.093: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.094: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.094: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Partial capture successful. Please touch the sensor again (18/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.094: Device reported enroll progress, reported 18 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.094: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.094: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.094: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.094: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.094: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.094: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.094: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.095: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.095: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.095: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.095: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.095: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.095: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.095: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.095: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.095: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.095: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.095: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.095: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.095: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.095: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.096: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Partial capture successful. Please touch the sensor again (19/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.096: Device reported enroll progress, reported 19 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.096: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.096: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.096: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.096: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.096: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.096: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.096: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.096: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.097: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.097: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.097: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.097: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.097: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.097: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.097: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.097: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Partial capture successful. Please touch the sensor again (20/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.097: Device reported enroll progress, reported 20 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.097: [egismoc] ENROLL_STATES entering state 12 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.097: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.097: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.098: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.098: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.098: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.098: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.098: [egismoc] ENROLL_STATES entering state 13 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.098: New fingerprint ID: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.098: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.098: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.098: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.098: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] ENROLL_STATES entering state 14 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] ENROLL_STATES entering state 15 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Enrollment was successful! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.099: Device reported enroll completion 185s (process:2457): libfprint-device-DEBUG: 00:01:17.099: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:2457): libfprint-device-DEBUG: 00:01:17.099: Print for finger FP_FINGER_LEFT_INDEX enrolled 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] ENROLL_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.099: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.099: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: List 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] LIST_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.099: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.099: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Device fingerprint 1: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] LIST_STATES entering state 1 185s (process:2457): libfprint-device-DEBUG: 00:01:17.100: Device reported listing completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] LIST_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.100: Completing action FPI_DEVICE_ACTION_LIST in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.100: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-device-DEBUG: 00:01:17.100: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Identify or Verify 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] IDENTIFY_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Device fingerprint 1: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] IDENTIFY_STATES entering state 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] IDENTIFY_STATES entering state 2 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.100: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.100: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.101: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.101: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.101: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.101: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.101: [egismoc] IDENTIFY_STATES entering state 3 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.101: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.101: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.101: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.101: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.101: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.101: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.101: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.101: [egismoc] IDENTIFY_STATES entering state 4 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.101: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.101: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.102: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.102: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.102: [egismoc] IDENTIFY_STATES entering state 5 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.102: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.102: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.102: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.102: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.102: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.102: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.102: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.102: [egismoc] IDENTIFY_STATES entering state 6 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.102: Get check command 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.102: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.102: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.102: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.102: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Identify check callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Identify successful for: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Verifying against: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-device-DEBUG: 00:01:17.103: Device reported verify result 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] IDENTIFY_STATES entering state 7 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] IDENTIFY_STATES entering state 8 185s (process:2457): libfprint-device-DEBUG: 00:01:17.103: Device reported verify completion 185s (process:2457): libfprint-device-DEBUG: 00:01:17.103: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] IDENTIFY_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.103: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.103: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-device-DEBUG: 00:01:17.103: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Identify or Verify 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] IDENTIFY_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.103: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.103: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.104: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.104: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.104: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.104: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.104: Device fingerprint 1: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.104: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.104: [egismoc] IDENTIFY_STATES entering state 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.104: [egismoc] IDENTIFY_STATES entering state 2 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.104: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.104: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.104: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.104: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.105: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.105: [egismoc] IDENTIFY_STATES entering state 3 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.105: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.105: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.105: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.105: [egismoc] IDENTIFY_STATES entering state 4 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.105: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.105: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.105: [egismoc] IDENTIFY_STATES entering state 5 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.105: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] IDENTIFY_STATES entering state 6 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Get check command 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Identify check callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Identify successful for: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-device-DEBUG: 00:01:17.106: Device reported identify result 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] IDENTIFY_STATES entering state 7 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.106: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.106: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.107: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.107: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.107: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.107: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.107: [egismoc] IDENTIFY_STATES entering state 8 185s (process:2457): libfprint-device-DEBUG: 00:01:17.107: Device reported identify completion 185s (process:2457): libfprint-device-DEBUG: 00:01:17.107: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.107: [egismoc] IDENTIFY_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.107: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.107: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.107: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-device-DEBUG: 00:01:17.107: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.107: Enroll 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.107: [egismoc] ENROLL_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.107: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.107: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.107: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.107: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.108: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Device fingerprint 1: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.108: [egismoc] ENROLL_STATES entering state 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.108: [egismoc] ENROLL_STATES entering state 2 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.108: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.108: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.108: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.108: [egismoc] ENROLL_STATES entering state 3 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.108: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.108: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.109: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.109: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.109: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.109: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.109: [egismoc] ENROLL_STATES entering state 4 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.109: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.109: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.109: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.109: [egismoc] ENROLL_STATES entering state 5 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.109: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.109: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.109: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.109: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] ENROLL_STATES entering state 6 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Get check command 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Enroll check callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Response suffix valid: NO 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.110: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 185s (process:2457): libfprint-device-DEBUG: 00:01:17.110: Device reported enroll completion 185s (process:2457): libfprint-device-DEBUG: 00:01:17.110: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:2457): libfprint-device-DEBUG: 00:01:17.110: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.110: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: List 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] LIST_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.110: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.110: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.111: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.111: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Device fingerprint 1: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.111: [egismoc] LIST_STATES entering state 1 185s (process:2457): libfprint-device-DEBUG: 00:01:17.111: Device reported listing completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.111: [egismoc] LIST_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.111: Completing action FPI_DEVICE_ACTION_LIST in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.111: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-device-DEBUG: 00:01:17.111: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Enroll 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.111: [egismoc] ENROLL_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.111: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.111: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.111: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.111: Device fingerprint 1: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] ENROLL_STATES entering state 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] ENROLL_STATES entering state 2 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] ENROLL_STATES entering state 3 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.112: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.112: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.113: [egismoc] ENROLL_STATES entering state 4 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.113: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.113: [egismoc] ENROLL_STATES entering state 5 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.113: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.113: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.113: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.113: [egismoc] ENROLL_STATES entering state 6 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Get check command 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.113: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.113: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.114: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.114: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Enroll check callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Response suffix valid: yes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.114: [egismoc] ENROLL_STATES entering state 7 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.114: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.114: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.114: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.114: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.114: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.114: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.115: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.115: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.115: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.115: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.115: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.115: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.115: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.115: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.115: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.115: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.115: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.115: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.115: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.115: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.116: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.116: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.116: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.116: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.116: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Partial capture successful. Please touch the sensor again (1/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.116: Device reported enroll progress, reported 1 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.116: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.116: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.116: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.116: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.117: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.117: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.117: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.117: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.117: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.117: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.117: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.117: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.117: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.117: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.118: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.118: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Partial capture successful. Please touch the sensor again (2/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.118: Device reported enroll progress, reported 2 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.118: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.118: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.118: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.118: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.118: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.118: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.118: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.119: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.119: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.119: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.119: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.119: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.119: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.119: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.119: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.119: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.119: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.119: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.119: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.119: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.119: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.120: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Partial capture successful. Please touch the sensor again (3/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.120: Device reported enroll progress, reported 3 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.120: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.120: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.120: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.120: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.120: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.120: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.120: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.120: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.121: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.121: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.121: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.121: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.121: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.121: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.121: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Partial capture successful. Please touch the sensor again (4/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.121: Device reported enroll progress, reported 4 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.121: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.121: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.121: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.122: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.122: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.122: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.122: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.122: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.122: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.122: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.122: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.122: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.122: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.122: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.122: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.122: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.122: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.123: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.123: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.123: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.123: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.123: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Partial capture successful. Please touch the sensor again (5/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.123: Device reported enroll progress, reported 5 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.123: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.123: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.123: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.123: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.124: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.124: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.124: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.124: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.124: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.124: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.124: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.124: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.124: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.124: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.124: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.124: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.124: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.125: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.125: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.125: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.125: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.125: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Partial capture successful. Please touch the sensor again (6/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.125: Device reported enroll progress, reported 6 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.125: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.125: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.125: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.125: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.126: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.126: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.126: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.126: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.126: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.126: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.126: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.126: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.126: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.126: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.126: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.127: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.127: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Partial capture successful. Please touch the sensor again (7/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.127: Device reported enroll progress, reported 7 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.127: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.127: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.127: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.127: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.127: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.127: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.127: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.128: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.128: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.128: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.128: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.128: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.128: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.128: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.128: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.128: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.128: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.128: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.128: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.128: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.128: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.129: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Response suffix valid: NO 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Response suffix valid: yes 185s (process:2457): libfprint-device-DEBUG: 00:01:17.129: Device reported enroll progress, reported 7 of 20 have been completed 185s listing - device should have prints 185s clear device storage 185s clear done 185s listing - device should be empty 185s enrolling 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 1, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 2, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 3, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 4, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 5, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 6, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 7, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 8, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 9, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 10, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 11, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 12, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 13, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 14, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 15, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 16, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 17, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 18, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 19, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 20, , None, None) 185s enroll done 185s listing - device should have 1 print 185s verifying 185s verify done 185s async identifying 185s indentification_done: 185s try to enroll duplicate 185s duplicate enroll attempt done 185s listing - device should still only have 1 print 185s enroll new finger 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 1, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 2, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 3, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 4, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 5, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 6, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 7, , None, None) 185s finger status: (process:2457): libfprint-SSM-DEBUG: 00:01:17.129: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.129: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.129: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.129: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.129: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.129: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.129: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.129: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.130: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.130: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.130: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.130: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.130: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.130: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.130: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.130: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.130: Partial capture successful. Please touch the sensor again (8/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.130: Device reported enroll progress, reported 8 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.131: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.131: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.131: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.132: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.132: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.132: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.132: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.132: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Partial capture successful. Please touch the sensor again (9/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.132: Device reported enroll progress, reported 9 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.132: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.132: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.132: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.132: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.133: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.133: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.133: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.133: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.133: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.133: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.133: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.133: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.133: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.133: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.133: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.134: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.134: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Response suffix valid: NO 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Response suffix valid: yes 185s (process:2457): libfprint-device-DEBUG: 00:01:17.134: Device reported enroll progress, reported 9 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.134: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.134: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.134: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.134: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.134: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.134: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.134: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.135: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.135: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.135: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.135: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.135: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.135: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.135: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.135: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.135: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.135: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.135: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.135: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.135: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.135: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.136: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Partial capture successful. Please touch the sensor again (10/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.136: Device reported enroll progress, reported 10 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.136: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.136: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.136: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.136: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.136: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.136: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.136: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.136: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.137: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.137: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.137: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.137: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.137: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.137: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.137: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.137: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Partial capture successful. Please touch the sensor again (11/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.137: Device reported enroll progress, reported 11 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.137: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.137: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.137: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.138: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.138: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.138: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.138: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.138: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.138: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.138: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.138: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.138: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.138: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.138: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.138: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.138: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.138: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.138: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.139: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.139: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.139: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.139: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.139: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Partial capture successful. Please touch the sensor again (12/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.139: Device reported enroll progress, reported 12 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.139: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.139: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.139: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.139: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.140: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.140: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.140: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.140: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.140: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.140: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.140: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.140: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.140: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.140: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.140: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.140: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.140: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.141: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.141: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.141: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.141: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.141: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Partial capture successful. Please touch the sensor again (13/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.141: Device reported enroll progress, reported 13 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.141: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.141: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.141: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.141: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.142: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.142: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.142: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.142: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.142: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.142: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.142: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.142: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.142: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.142: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.142: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.143: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.143: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Partial capture successful. Please touch the sensor again (14/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.143: Device reported enroll progress, reported 14 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.143: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.143: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.143: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.143: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.143: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.143: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.143: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.144: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.144: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.144: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.144: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.144: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.144: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.144: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.144: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.144: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.144: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.144: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.144: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.144: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.145: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Partial capture successful. Please touch the sensor again (15/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.145: Device reported enroll progress, reported 15 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.145: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.145: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.145: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.145: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.145: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.145: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.145: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.145: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.146: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.146: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.146: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.146: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.146: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.146: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.146: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.146: Partial capture successful. Please touch the sensor again (16/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.146: Device reported enroll progress, reported 16 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.147: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.147: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.147: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.147: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.147: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.147: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.147: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.147: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.147: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.147: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.147: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.147: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.147: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.147: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.148: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.148: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.148: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.148: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.148: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.148: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.148: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Partial capture successful. Please touch the sensor again (17/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.148: Device reported enroll progress, reported 17 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.148: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.148: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.148: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.149: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.149: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.149: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.149: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.149: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.149: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.149: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.149: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.149: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.149: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.149: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.149: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.149: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.149: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.150: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.150: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.150: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.150: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.150: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Partial capture successful. Please touch the sensor again (18/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.150: Device reported enroll progress, reported 18 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.150: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.150: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.150: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.150: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.151: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.151: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.151: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.151: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.151: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.151: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.151: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.151: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.151: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.151: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.152: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.152: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Partial capture successful. Please touch the sensor again (19/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.152: Device reported enroll progress, reported 19 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.152: [egismoc] ENROLL_STATES entering state 8 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.152: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.152: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.152: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.152: [egismoc] ENROLL_STATES entering state 9 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.152: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.152: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.153: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.153: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.153: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.153: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.153: [egismoc] ENROLL_STATES entering state 10 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.153: Wait for finger on sensor 185s (process:2457): libfprint-device-DEBUG: 00:01:17.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.153: Finger on sensor callback 185s (process:2457): libfprint-device-DEBUG: 00:01:17.153: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.153: [egismoc] ENROLL_STATES entering state 11 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.153: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.153: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.153: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.153: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.154: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Read capture callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Response prefix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Response suffix valid: yes 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Partial capture successful. Please touch the sensor again (20/20) 185s (process:2457): libfprint-device-DEBUG: 00:01:17.154: Device reported enroll progress, reported 20 of 20 have been completed 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.154: [egismoc] ENROLL_STATES entering state 12 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.154: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.154: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.154: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.154: [egismoc] ENROLL_STATES entering state 13 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: New fingerprint ID: FP1-00000000-7-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.154: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.154: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.154: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] ENROLL_STATES entering state 14 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Task SSM next state callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] ENROLL_STATES entering state 15 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Enrollment was successful! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.155: Device reported enroll completion 185s (process:2457): libfprint-device-DEBUG: 00:01:17.155: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:2457): libfprint-device-DEBUG: 00:01:17.155: Print for finger FP_FINGER_RIGHT_INDEX enrolled 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] ENROLL_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.155: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.155: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: List 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] LIST_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.155: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.155: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Device fingerprint 1: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Device fingerprint 2: FP1-00000000-7-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Number of currently enrolled fingerprints on the device is 2 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] LIST_STATES entering state 1 185s (process:2457): libfprint-device-DEBUG: 00:01:17.156: Device reported listing completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] LIST_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.156: Completing action FPI_DEVICE_ACTION_LIST in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.156: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Delete 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] DELETE_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Device fingerprint 1: FP1-00000000-2-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Device fingerprint 2: FP1-00000000-7-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Number of currently enrolled fingerprints on the device is 2 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] DELETE_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Get delete command 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.156: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.156: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.157: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.157: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.157: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.157: Delete callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.157: Response prefix valid: yes 185s (process:2457): libfprint-device-DEBUG: 00:01:17.157: Device reported deletion completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.157: [egismoc] DELETE_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.157: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.157: Completing action FPI_DEVICE_ACTION_DELETE in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.157: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.157: List 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.157: [egismoc] LIST_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.157: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.157: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.157: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.157: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.157: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.157: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Device fingerprint 1: FP1-00000000-7-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] LIST_STATES entering state 1 185s (process:2457): libfprint-device-DEBUG: 00:01:17.158: Device reported listing completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] LIST_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.158: Completing action FPI_DEVICE_ACTION_LIST in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.158: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Clear storage 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] DELETE_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Device fingerprint 1: FP1-00000000-7-00000000-nobody 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Number of currently enrolled fingerprints on the device is 1 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] DELETE_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Get delete command 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.158: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.158: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.159: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Delete callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Response prefix valid: yes 185s (process:2457): libfprint-device-DEBUG: 00:01:17.159: Device reported deletion completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.159: [egismoc] DELETE_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.159: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.159: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: List 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.159: [egismoc] LIST_STATES entering state 0 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Execute command and get response 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Get check bytes 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.159: [egismoc] CMD_STATES entering state 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.159: [egismoc] CMD_STATES entering state 1 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Command receive callback 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.159: [egismoc] CMD_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: List callback 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Number of currently enrolled fingerprints on the device is 0 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.159: [egismoc] LIST_STATES entering state 1 185s (process:2457): libfprint-device-DEBUG: 00:01:17.159: Device reported listing completion 185s (process:2457): libfprint-SSM-DEBUG: 00:01:17.159: [egismoc] LIST_STATES completed successfully 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Task SSM done 185s (process:2457): libfprint-device-DEBUG: 00:01:17.159: Completing action FPI_DEVICE_ACTION_LIST in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.159: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Closing device 185s (process:2457): libfprint-egismoc-DEBUG: 00:01:17.159: Cancel 185s (process:2457): libfprint-device-DEBUG: 00:01:17.159: Device reported close completion 185s (process:2457): libfprint-device-DEBUG: 00:01:17.160: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 185s (process:2457): libfprint-device-DEBUG: 00:01:17.160: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 8, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 9, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 10, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 11, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 12, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 13, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 14, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 15, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 16, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 17, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 18, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 19, , None, None) 185s finger status: 185s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff93c0e3c0 (FpiDeviceEgisMoc at 0x2101950)>, 20, , None, None) 185s enroll new finger done 185s listing - device should have 2 prints 185s deleting first print 185s delete done 185s listing - device should only have second print 185s clear device storage 185s clear done 185s listing - device should be empty 185s ** (umockdev-run:2453): DEBUG: 00:01:17.174: umockdev.vala:154: Removing test bed /tmp/umockdev.SZKJ22 185s (umockdev-run:2453): GLib-DEBUG: 00:01:17.176: unsetenv() is not thread-safe and should not be used after threads are created 185s PASS: libfprint-2/driver-egismoc-0586.test 185s Running test: libfprint-2/driver-vfs7552.test 185s ** (umockdev-run:2465): DEBUG: 00:01:17.209: umockdev.vala:127: Created udev test bed /tmp/umockdev.Z4M212 185s ** (umockdev-run:2465): DEBUG: 00:01:17.209: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 185s ** (umockdev-run:2465): DEBUG: 00:01:17.211: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 185s ** (umockdev-run:2465): DEBUG: 00:01:17.213: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z4M212/dev/bus/usb/001/003 185s ** (umockdev-run:2465): DEBUG: 00:01:17.213: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 185s ** (umockdev-run:2465): DEBUG: 00:01:17.214: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 185s ** (umockdev-run:2465): DEBUG: 00:01:17.215: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z4M212/dev/bus/usb/001/001 185s ** (umockdev-run:2465): DEBUG: 00:01:17.215: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 185s ** (umockdev-run:2465): DEBUG: 00:01:17.216: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 185s (umockdev-run:2465): GLib-GIO-DEBUG: 00:01:17.217: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 185s (process:2469): libfprint-context-DEBUG: 00:01:17.294: Initializing FpContext (libfprint version 1.94.8+tod1) 185s (process:2469): libfprint-tod-DEBUG: 00:01:17.294: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 185s (process:2469): libfprint-context-DEBUG: 00:01:17.295: No driver found for USB device 1D6B:0002 185s (process:2469): libfprint-device-DEBUG: 00:01:17.295: Device reported probe completion 185s (process:2469): libfprint-device-DEBUG: 00:01:17.295: Completing action FPI_DEVICE_ACTION_PROBE in idle! 185s (process:2469): libfprint-device-DEBUG: 00:01:17.295: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.296: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.296: [vfs7552] DEVICE OPEN entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.296: Sending vfs7552_cmd_01 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.296: [vfs7552] DEVICE OPEN entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.296: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.296: Got 38 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.296: [vfs7552] DEVICE OPEN entering state 2 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.296: Sending vfs7552_cmd_19 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.297: [vfs7552] DEVICE OPEN entering state 3 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.297: Receiving 128 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.297: Got 68 bytes out of 128 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.297: [vfs7552] DEVICE OPEN entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.297: Sending vfs7552_init_00 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.297: [vfs7552] DEVICE OPEN entering state 5 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.298: Receiving 64 bytes 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.298: [vfs7552] DEVICE OPEN entering state 6 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.298: Sending vfs7552_init_01 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.298: [vfs7552] DEVICE OPEN entering state 7 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.298: Receiving 64 bytes 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.298: [vfs7552] DEVICE OPEN entering state 8 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.298: Sending vfs7552_init_02 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.299: [vfs7552] DEVICE OPEN entering state 9 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.299: Receiving 64 bytes 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.299: [vfs7552] DEVICE OPEN entering state 10 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.299: Sending vfs7552_init_03 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.300: [vfs7552] DEVICE OPEN entering state 11 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.300: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.300: Got 10 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.300: [vfs7552] DEVICE OPEN entering state 12 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.300: Sending vfs7552_init_04 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.300: [vfs7552] DEVICE OPEN entering state 13 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.300: Receiving 64 bytes 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.301: [vfs7552] DEVICE OPEN completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.301: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 185s (process:2469): libfprint-image_device-DEBUG: 00:01:17.301: Image device open completed 185s (process:2469): libfprint-device-DEBUG: 00:01:17.301: Device reported open completion 185s (process:2469): libfprint-device-DEBUG: 00:01:17.301: Completing action FPI_DEVICE_ACTION_OPEN in idle! 185s (process:2469): libfprint-device-DEBUG: 00:01:17.301: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2469): libfprint-device-DEBUG: 00:01:17.301: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 185s (process:2469): libfprint-image_device-DEBUG: 00:01:17.301: Activating image device 185s (process:2469): libfprint-image_device-DEBUG: 00:01:17.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 185s (process:2469): libfprint-image_device-DEBUG: 00:01:17.301: Image device activation completed 185s (process:2469): libfprint-image_device-DEBUG: 00:01:17.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 185s (process:2469): libfprint-image_device-DEBUG: 00:01:17.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 185s (process:2469): libfprint-device-DEBUG: 00:01:17.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.351: changing to 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.351: [vfs7552] ACTIVATE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.351: [vfs7552] ACTIVATE INIT entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.351: Sending vfs7552_image_start 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.351: [vfs7552] ACTIVATE INIT entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.351: Receiving 2048 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.352: Got 1962 bytes out of 2048 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE INIT completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.352: Receiving 8 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.352: Got 5 bytes out of 8 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.352: Receiving 8 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.352: Got 5 bytes out of 8 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] ACTIVATE_NUM_STATES completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.352: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.352: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.353: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.353: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.353: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.353: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.353: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.353: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.354: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.354: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.354: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.354: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.354: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.354: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.354: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.354: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.355: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.355: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.355: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.355: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.355: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.355: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.356: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.356: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.356: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.356: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.356: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.356: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.357: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.357: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.357: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.357: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.357: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.357: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.357: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.357: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.358: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.358: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.358: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.358: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.358: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.358: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.358: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.358: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.359: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.359: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.359: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.359: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.359: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.359: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.359: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.359: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.360: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.360: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.360: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.360: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.360: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.360: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.360: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.361: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.361: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.361: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.361: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.361: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.361: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.361: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.362: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.362: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.362: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.362: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.362: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.362: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.363: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.363: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.363: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.363: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.363: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.363: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.364: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.364: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.364: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.364: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.364: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.364: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.364: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.364: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.365: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.365: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.365: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.365: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.365: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.365: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.365: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.365: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.366: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.366: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.366: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.366: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.366: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.366: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.366: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.366: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.367: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.367: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.367: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.367: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.367: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.367: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.367: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.368: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.368: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.368: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.368: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.368: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.368: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.368: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.369: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.369: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.369: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.369: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.369: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.369: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.370: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.370: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.370: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.370: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.370: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.370: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.371: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.371: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.371: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.371: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.371: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.371: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.372: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.372: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.372: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.372: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.372: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.372: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.373: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.373: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.373: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.373: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.373: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.373: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.373: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.373: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.374: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.374: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.374: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.374: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.374: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.374: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.375: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.375: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.375: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.375: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.375: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.375: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.375: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.376: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.376: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.376: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.376: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.376: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.377: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.377: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.377: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.377: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.377: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.377: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.377: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.378: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.378: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.378: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.378: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.378: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.378: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.378: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.379: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.379: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.379: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.379: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.379: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.379: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.380: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.380: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.380: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.380: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.380: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.380: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.381: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.381: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.381: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.381: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.381: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.381: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.381: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.382: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.382: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.382: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.382: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.382: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.382: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.382: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.383: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.383: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.383: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.383: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.383: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.383: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.384: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.384: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.384: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.384: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.384: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.384: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.384: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.384: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.385: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.385: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.385: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.385: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.385: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.385: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.386: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.386: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.386: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.386: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.386: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.386: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.387: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.387: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.387: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.387: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.387: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.387: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.388: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.388: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.388: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.388: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.388: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.388: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.388: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.388: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.389: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.389: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.389: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.389: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.389: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.389: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.390: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.390: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.390: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.390: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.390: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.390: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.390: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.390: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.391: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.391: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.391: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.391: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.391: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.391: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.392: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.392: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.392: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.392: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.392: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.392: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.393: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.393: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.393: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.393: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.393: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.393: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.393: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.393: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.394: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.394: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.394: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.394: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.394: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.394: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.395: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.395: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.395: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.395: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.395: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.395: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.396: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.396: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.396: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.396: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.396: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.396: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.397: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.397: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.397: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.397: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.397: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.397: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.397: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.397: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.398: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.398: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.398: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.398: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.398: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.398: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.399: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.399: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.399: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.399: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.399: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.399: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.400: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.400: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.400: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.400: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.400: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.400: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.400: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.400: Receiving 64 bytes 185s (process:2469): libfprint-device-DEBUG: 00:01:17.401: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.401: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.401: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.401: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.401: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.401: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.401: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.402: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.402: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.402: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.402: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.402: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.402: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.403: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.403: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.403: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.403: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.403: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.403: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.403: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.404: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.404: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.404: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.404: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.404: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.404: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.404: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.405: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.405: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.405: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.405: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.405: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.405: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.406: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.406: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.406: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.406: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.406: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.406: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.407: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.407: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.407: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.407: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.407: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.407: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.407: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.407: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.408: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.408: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.408: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.408: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.408: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.408: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.408: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.408: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.409: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.409: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.409: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.409: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.409: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.409: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.409: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.409: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.410: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.410: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.410: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.410: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.410: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.410: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.410: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.410: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.411: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.411: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.411: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.411: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.411: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.411: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.411: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.411: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.412: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.412: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.412: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.412: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.412: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.412: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.412: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.412: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.413: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.413: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.413: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.413: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.413: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.413: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.413: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.413: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.414: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.414: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.414: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.414: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.414: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.414: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.414: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.414: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.415: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.415: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.415: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.415: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.415: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.415: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.415: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.415: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.416: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.416: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.416: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.416: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.416: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.416: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.416: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.416: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.417: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.417: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.417: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.417: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.417: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.417: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.418: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.418: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.418: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.418: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.418: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.418: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.419: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.419: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.419: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.419: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.419: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.419: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.420: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.420: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.420: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.420: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.420: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.420: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.420: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.420: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.421: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.421: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.421: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.421: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.421: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.421: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.422: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.422: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.422: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.422: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.422: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.422: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.423: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.423: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.423: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.423: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.423: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.423: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.423: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.423: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.423: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.424: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.424: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.424: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.424: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.424: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.424: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.424: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.424: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.425: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.425: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.425: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.425: variance_before = 396 185s 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.425: background stored 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.425: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.425: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.426: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.426: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.426: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.426: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.426: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.426: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.426: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.426: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.427: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.427: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.427: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.427: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.427: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.427: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.428: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.428: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.428: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.428: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.428: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.428: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.429: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.429: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.429: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.429: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.429: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.429: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.429: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.429: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.430: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.430: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.430: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.430: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.430: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.430: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.430: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.430: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.431: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.431: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.431: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.431: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.431: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.431: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.431: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.431: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.432: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.432: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.432: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.432: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.432: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.432: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.432: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.432: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.433: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.433: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.433: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.433: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.433: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.433: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.434: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.434: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.434: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.434: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.434: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.434: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.434: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.435: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.435: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.435: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.435: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.435: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.435: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.435: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.436: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.436: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.436: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.436: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.436: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.436: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.437: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.437: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.437: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.437: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.437: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.437: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.437: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.437: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.438: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.438: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.438: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.438: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.438: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.438: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.439: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.439: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.439: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.439: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.439: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.439: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.440: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.440: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.440: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.440: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.440: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.440: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.440: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.440: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.441: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.441: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.441: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.441: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.441: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.441: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.442: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.442: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.442: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.442: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.442: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.442: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.443: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.443: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.443: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.443: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.443: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.443: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.443: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.443: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.444: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.444: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.444: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.444: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.444: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.444: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.444: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.444: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.445: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.445: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.445: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.445: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.445: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.445: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.445: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.445: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.446: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.446: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.446: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.446: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.446: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.446: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.446: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.446: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.447: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.447: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.447: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.447: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.447: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.447: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.448: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.448: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.448: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.448: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.448: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.448: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.449: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.449: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.449: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.449: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.449: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.449: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.449: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.449: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.450: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.450: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.450: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.450: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.450: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.450: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.450: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.451: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.451: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.451: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.451: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.451: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.452: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.452: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.452: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.452: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.452: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.452: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.452: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.452: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.453: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.453: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.453: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.453: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.453: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.453: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.454: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.454: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.454: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.454: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.454: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.454: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.455: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.455: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.455: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.455: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.455: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.455: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.456: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.456: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.456: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.456: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.456: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.456: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.457: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.457: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.457: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.457: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.457: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.457: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.458: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.458: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.458: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.458: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.458: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.458: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.459: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.459: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.459: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.459: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.459: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.459: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.460: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.460: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.460: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.460: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.460: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.460: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.461: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.461: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.461: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.461: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.461: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.461: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.462: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.462: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.462: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.462: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.462: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.462: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.462: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.462: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.463: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.463: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.463: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.463: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.463: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.463: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.464: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.464: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.464: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.464: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.464: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.464: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.465: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.465: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.465: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.465: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.465: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.465: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.466: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.466: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.466: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.466: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.466: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.466: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.466: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.466: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.467: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.467: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.467: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.467: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.467: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.467: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.468: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.468: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.468: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.468: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.468: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.468: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.469: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.469: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.469: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.469: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.469: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.469: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.469: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.469: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.470: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.470: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.470: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.470: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.470: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.470: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.471: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.471: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.471: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.471: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.471: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.471: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.471: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.472: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.472: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.472: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.472: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.472: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.472: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.472: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.472: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.473: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.473: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.473: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.473: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.473: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.473: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.474: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.474: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.474: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.474: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.474: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.474: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.474: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.475: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.475: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.475: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.475: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.475: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.475: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.476: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.476: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.476: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.476: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.476: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.476: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.476: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.476: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.477: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.477: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.477: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.477: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.477: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.477: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.478: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.478: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.478: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.478: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.478: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.478: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.479: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.479: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.479: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.479: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.479: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.479: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.479: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.480: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.480: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.480: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.480: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.480: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.480: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.480: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.480: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.481: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.481: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.481: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.481: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.481: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.481: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.482: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.482: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.482: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.482: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.482: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.482: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.483: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.483: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.483: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.483: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.483: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.483: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.483: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.483: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.484: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.484: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.484: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.484: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.484: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.484: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.485: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.485: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.485: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.485: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.485: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.485: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.485: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.485: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.486: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.486: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.486: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.486: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.486: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.486: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.487: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.487: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.487: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.487: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.487: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.487: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.488: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.488: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.488: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.488: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.488: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.488: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.489: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.489: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.489: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.489: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.489: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.489: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.489: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.489: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.490: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.490: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.490: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.490: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.490: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.490: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.491: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.491: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.491: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.491: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.491: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.491: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.492: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.492: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.492: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.492: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.492: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.492: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.493: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.493: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.493: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.493: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.493: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.493: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.493: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.493: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.494: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.494: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.494: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.494: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.494: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.494: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.495: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.495: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.495: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.495: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.495: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.495: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.496: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.496: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.496: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.496: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.496: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.496: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.497: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.497: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.497: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.497: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.497: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.497: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.497: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.497: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.498: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.498: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.498: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.498: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.498: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.498: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.499: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.499: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.499: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.499: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.499: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.499: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.500: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.500: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.500: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.500: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.500: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.500: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.500: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.500: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.501: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.501: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.501: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.501: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.501: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.501: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.502: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.502: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.502: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.502: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.502: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.502: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.503: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.503: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.503: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.503: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.503: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.503: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.504: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.504: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.504: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.504: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.504: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.504: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.504: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.504: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.504: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.505: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.505: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.505: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.505: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.505: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.506: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.506: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.506: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.506: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.506: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.506: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.506: Cleaning image 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.506: variance_after = 20 185s 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.506: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.506: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.507: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.507: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.507: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.507: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.507: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.507: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.508: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.508: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.508: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.508: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.508: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.508: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.508: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.508: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.509: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.509: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.509: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.509: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.509: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.509: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.510: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.510: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.510: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.510: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.510: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.510: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.511: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.511: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.511: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.511: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.511: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.511: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.511: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.511: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.512: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.512: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.512: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.512: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.512: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.512: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.512: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.513: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.513: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.513: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.513: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.513: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.514: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.514: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.514: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.514: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.514: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.514: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.514: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.514: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.515: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.515: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.515: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.515: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.515: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.515: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.516: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.516: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.516: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.516: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.516: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.516: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.517: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.517: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.517: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.517: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.517: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.517: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.518: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.518: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.518: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.518: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.518: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.518: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.518: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.518: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.519: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.519: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.519: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.519: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.519: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.519: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.520: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.520: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.520: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.520: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.520: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.520: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.521: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.521: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.521: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.521: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.521: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.521: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.521: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.521: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.522: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.522: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.522: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.522: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.522: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.522: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.523: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.523: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.523: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.523: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.523: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.523: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.524: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.524: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.524: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.524: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.524: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.524: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.525: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.525: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.525: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.525: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.525: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.525: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.525: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.525: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.526: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.526: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.526: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.526: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.526: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.526: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.527: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.527: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.527: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.527: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.527: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.527: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.528: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.528: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.528: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.528: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.528: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.528: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.528: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.528: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.529: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.529: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.529: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.529: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.529: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.529: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.530: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.530: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.530: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.530: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.530: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.530: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.531: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.531: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.531: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.531: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.531: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.531: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.532: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.532: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.532: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.532: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.532: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.532: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.532: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.532: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.533: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.533: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.533: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.533: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.533: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.533: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.534: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.534: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.534: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.534: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.534: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.534: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.535: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.535: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.535: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.535: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.535: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.535: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.535: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.535: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.536: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.536: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.536: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.536: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.536: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.536: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.537: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.537: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.537: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.537: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.537: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.537: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.538: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.538: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.538: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.538: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.538: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.538: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.538: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.538: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.539: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.539: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.539: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.539: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.539: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.539: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.540: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.540: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.540: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.540: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.540: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.540: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.541: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.541: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.541: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.541: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.541: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.541: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.541: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.541: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.542: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.542: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.542: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.542: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.542: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.542: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.543: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.543: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.543: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.543: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.543: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.543: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.544: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.544: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.544: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.544: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.544: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.544: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.544: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.545: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.545: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.545: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.545: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.545: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.545: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.545: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.546: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.546: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.546: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.546: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.546: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.546: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.547: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.547: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.547: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.547: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.547: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.547: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.548: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.548: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.548: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.548: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.548: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.548: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.548: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.548: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.549: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.549: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.549: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.549: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.549: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.550: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.550: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.550: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.550: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.550: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.550: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.550: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.551: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.551: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.551: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.551: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.551: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.551: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.551: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.551: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.552: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.552: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.552: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.552: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.552: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.552: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.553: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.553: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.553: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.553: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.553: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.553: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.554: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.554: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.554: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.554: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.554: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.554: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.554: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.555: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.555: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.555: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.555: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.555: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.555: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.555: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.556: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.556: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.556: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.556: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.556: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.556: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.556: Cleaning image 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.557: variance_after = 18 185s 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.557: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.557: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.557: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.557: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.557: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.557: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.557: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.557: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.558: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.558: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.558: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.558: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.558: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.558: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.559: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.559: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.559: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.559: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.559: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.559: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.559: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.559: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.560: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.560: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.560: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.560: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.560: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.560: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.560: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.561: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.561: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.561: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.561: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.561: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.562: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.562: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.562: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.562: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.562: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.562: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.562: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.562: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.563: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.563: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.563: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.563: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.563: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.563: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.564: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.564: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.564: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.564: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.564: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.564: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.565: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.565: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.565: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.565: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.565: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.565: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.565: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.565: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.566: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.566: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.566: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.566: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.566: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.566: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.567: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.567: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.567: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.567: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.567: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.567: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.568: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.568: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.568: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.568: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.568: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.568: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.568: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.568: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.569: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.569: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.569: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.569: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.569: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.569: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.570: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.570: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.570: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.570: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.570: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.570: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.571: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.571: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.571: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.571: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.571: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.571: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.572: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.572: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.572: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.572: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.572: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.572: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.572: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.572: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.573: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.573: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.573: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.573: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.573: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.573: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.574: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.574: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.574: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.574: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.574: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.574: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.575: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.575: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.575: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.575: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.575: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.575: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.575: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.575: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.576: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.576: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.576: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.576: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.576: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.576: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.577: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.577: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.577: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.577: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.577: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.577: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.578: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.578: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.578: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.578: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.578: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.578: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.579: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.579: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.579: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.579: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.579: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.579: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.579: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.579: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.580: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.580: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.580: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.580: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.580: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.580: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.581: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.581: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.581: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.581: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.581: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.581: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.582: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.582: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.582: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.582: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.582: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.582: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.582: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.582: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.583: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.583: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.583: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.583: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.583: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.583: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.584: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.584: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.584: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.584: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.584: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.584: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.585: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.585: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.585: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.585: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.585: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.585: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.585: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.585: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.586: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.586: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.586: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.586: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.586: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.586: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.587: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.587: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.587: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.587: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.587: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.587: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.588: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.588: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.588: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.588: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.588: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.588: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.589: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.589: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.589: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.589: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.589: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.589: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.589: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.589: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.590: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.590: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.590: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.590: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.590: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.590: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.591: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.591: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.591: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.591: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.591: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.591: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.592: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.592: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.592: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.592: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.592: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.592: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.592: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.592: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.593: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.593: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.593: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.593: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.593: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.593: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.594: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.594: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.594: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.594: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.594: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.594: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.595: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.595: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.595: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.595: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.595: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.595: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.596: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.596: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.596: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.596: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.596: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.596: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.596: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.596: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.597: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.597: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.597: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.597: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.597: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.597: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.598: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.598: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.598: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.598: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.598: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.598: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.599: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.599: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.599: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.599: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.599: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.599: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.599: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.599: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.600: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.600: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.600: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.600: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.600: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.600: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.601: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.601: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.601: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.601: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.601: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.601: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.602: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.602: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.602: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.602: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.602: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.602: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.602: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.602: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.603: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.603: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.603: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.603: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.603: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.603: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.604: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.604: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.604: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.604: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.604: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.604: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.605: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.605: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.605: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.605: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.605: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.605: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.605: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.605: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.606: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.606: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.606: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.606: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.606: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.606: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.607: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.607: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.607: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.607: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.607: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.607: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.608: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.608: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.608: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.608: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.608: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.608: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.609: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.609: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.609: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.609: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.609: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.609: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.609: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.609: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.610: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.610: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.610: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.610: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.610: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.610: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.611: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.611: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.611: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.611: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.611: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.611: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.612: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.612: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.612: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.612: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.612: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.612: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.612: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.612: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.613: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.613: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.613: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.613: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.613: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.613: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.614: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.614: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.614: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.614: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.614: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.614: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.615: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.615: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.615: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.615: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.615: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.615: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.615: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.615: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.616: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.616: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.616: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.616: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.616: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.616: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.617: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.617: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.617: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.617: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.617: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.617: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.618: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.618: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.618: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.618: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.618: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.618: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.618: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.618: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.619: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.619: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.619: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.619: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.619: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.619: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.620: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.620: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.620: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.620: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.620: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.620: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.621: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.621: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.621: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.621: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.621: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.621: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.621: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.621: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.622: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.622: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.622: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.622: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.622: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.622: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.623: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.623: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.623: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.623: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.623: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.623: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.624: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.624: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.624: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.624: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.624: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.624: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.624: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.624: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.625: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.625: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.625: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.625: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.625: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.625: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.626: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.626: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.626: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.626: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.626: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.626: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.627: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.627: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.627: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.627: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.627: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.627: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.628: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.628: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.628: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.628: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.628: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.628: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.628: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.628: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.629: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.629: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.629: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.629: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.629: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.629: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.630: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.630: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.630: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.630: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.630: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.630: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.631: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.631: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.631: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.631: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.631: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.631: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.632: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.632: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.632: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.632: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.632: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.632: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.632: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.632: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.633: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.633: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.633: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.633: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.633: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.633: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.634: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.634: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.634: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.634: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.634: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.634: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.635: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.635: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.635: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.635: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.635: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.635: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.635: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.635: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.636: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.636: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.636: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.636: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.636: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.636: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.637: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.637: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.637: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.637: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.637: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.637: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.638: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.638: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.638: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.638: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.638: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.638: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.639: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.639: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.639: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.639: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.639: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.639: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.640: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.640: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.640: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.640: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.640: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.640: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.641: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.641: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.641: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.641: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.641: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.641: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.641: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.641: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.642: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.642: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.642: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.642: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.642: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.642: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.642: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.642: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.643: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.643: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.644: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.644: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.644: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.644: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.644: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.644: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.645: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.645: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.645: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.645: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.645: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.645: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.646: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.646: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.646: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.646: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.646: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.646: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.647: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.647: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.647: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.647: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.647: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.647: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.648: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.648: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.648: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.648: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.648: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.648: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.649: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.649: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.649: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.649: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.649: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.649: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.650: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.650: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.650: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.650: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.650: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.650: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.651: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.651: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.651: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.651: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.651: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.651: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.652: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.652: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.652: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.652: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.652: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.652: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.652: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.652: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.653: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.653: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.653: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.653: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.653: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.653: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.654: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.654: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.654: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.654: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.654: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.654: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.655: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.655: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.655: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.655: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.655: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.655: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.655: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.655: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.656: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.656: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.656: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.656: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.656: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.656: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.656: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.657: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.657: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.657: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.657: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.657: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.657: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.658: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.658: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.658: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.658: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.658: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.658: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.658: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.658: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.659: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.659: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.659: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.659: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.659: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.659: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.660: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.660: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.660: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.660: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.660: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.660: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.660: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.661: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.661: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.661: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.661: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.661: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.661: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.661: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.661: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.662: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.662: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.662: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.662: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.662: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.662: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.663: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.663: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.663: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.663: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.663: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.663: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.663: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.663: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.664: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.664: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.664: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.664: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.664: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.664: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.665: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.665: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.665: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.665: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.665: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.665: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.666: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.666: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.666: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.666: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.666: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.666: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.666: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.666: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.666: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.667: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.667: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.667: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.667: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.667: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.667: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.668: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.668: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.668: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.668: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.668: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.668: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.669: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.669: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.669: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.669: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.669: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.669: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.669: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.669: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.670: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.670: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.670: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.670: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.670: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.670: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.671: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.671: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.671: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.671: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.671: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.671: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.672: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.672: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.672: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.672: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.672: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.672: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.672: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.672: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.673: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.673: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.673: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.673: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.673: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.673: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.674: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.674: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.674: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.674: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.674: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.674: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.675: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.675: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.675: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.675: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.675: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.675: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.676: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.676: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.676: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.676: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.676: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.676: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.676: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.676: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.677: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.677: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.677: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.677: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.677: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.677: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.678: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.678: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.678: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.678: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.678: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.678: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.678: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.678: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.679: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.679: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.679: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.679: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.679: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.679: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.680: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.680: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.680: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.680: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.680: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.680: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.681: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.681: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.681: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.681: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.681: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.681: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.682: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.682: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.682: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.682: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.682: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.682: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.682: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.682: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.683: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.683: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.683: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.683: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.683: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.683: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.684: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.684: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.684: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.684: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.684: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.684: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.685: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.685: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.685: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.685: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.685: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.685: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.685: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.685: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.686: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.686: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.686: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.686: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.686: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.686: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.687: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.687: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.687: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.687: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.687: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.687: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.688: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.688: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.688: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.688: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.688: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.688: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.688: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.688: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.689: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.689: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.689: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.689: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.689: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.689: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.690: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.690: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.690: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.690: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.690: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.690: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.690: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.691: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.691: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.691: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.691: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.691: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.691: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.691: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.692: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.692: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.692: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.692: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.692: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.693: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.693: Cleaning image 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.693: variance_after = 20 185s 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.693: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.693: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.693: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.693: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.693: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.693: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.693: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.693: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.694: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.694: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.694: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.694: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.694: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.694: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.695: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.695: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.695: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.695: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.695: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.695: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.695: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.695: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.696: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.696: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.696: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.696: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.696: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.696: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.697: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.697: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.697: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.697: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.697: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.697: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.698: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.698: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.698: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.698: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.698: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.698: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.699: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.699: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.699: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.699: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.699: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.699: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.699: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.699: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.700: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.700: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.700: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.700: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.700: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.700: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.701: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.701: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.701: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.701: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.701: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.701: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.702: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.702: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.702: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.702: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.702: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.702: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.703: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.703: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.703: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.703: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.703: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.703: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.704: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.704: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.704: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.704: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.704: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.704: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.704: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.704: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.705: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.705: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.705: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.705: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.705: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.705: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.706: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.706: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.706: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.706: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.706: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.706: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.707: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.707: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.707: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.707: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.707: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.707: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.707: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.707: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.708: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.708: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.708: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.708: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.708: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.708: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.709: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.709: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.709: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.709: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.709: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.709: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.710: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.710: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.710: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.710: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.710: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.710: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.710: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.710: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.711: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.711: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.711: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.711: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.711: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.711: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.712: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.712: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.712: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.712: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.712: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.712: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.713: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.713: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.713: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.713: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.713: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.713: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.714: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.714: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.714: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.714: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.714: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.714: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.714: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.714: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.715: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.715: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.715: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.715: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.715: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.715: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.716: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.716: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.716: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.716: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.716: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.716: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.717: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.717: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.717: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.717: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.717: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.717: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.717: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.717: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.718: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.718: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.718: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.718: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.718: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.718: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.719: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.719: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.719: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.719: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.719: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.719: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.720: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.720: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.720: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.720: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.720: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.720: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.721: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.721: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.721: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.721: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.721: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.721: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.721: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.721: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.722: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.722: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.722: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.722: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.722: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.723: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.723: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.723: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.723: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.723: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.723: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.723: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.724: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.724: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.724: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.724: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.724: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.724: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.724: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.724: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.725: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.725: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.725: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.725: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.725: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.725: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.726: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.726: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.726: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.726: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.726: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.726: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.727: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.727: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.727: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.727: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.727: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.727: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.728: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.728: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.728: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.728: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.728: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.728: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.728: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.728: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.729: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.729: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.729: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.729: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.729: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.729: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.730: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.730: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.730: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.730: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.730: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.730: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.731: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.731: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.731: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.731: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.731: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.731: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.731: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.731: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.732: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.732: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.732: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.732: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.732: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.732: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.733: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.733: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.733: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.733: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.733: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.733: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.734: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.734: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.734: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.734: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.734: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.734: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.735: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.735: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.735: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.735: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.735: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.735: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.735: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.735: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.735: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.736: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.736: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.736: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.736: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.736: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.736: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.736: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.736: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.737: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.737: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.737: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.737: Cleaning image 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.737: variance_after = 18 185s 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.737: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.737: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.738: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.738: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.738: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.738: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.738: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.738: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.738: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.738: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.739: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.739: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.739: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.739: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.739: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.739: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.740: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.740: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.740: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.740: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.740: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.740: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.741: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.741: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.741: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.741: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.741: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.741: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.742: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.742: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.742: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.742: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.742: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.742: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.742: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.742: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.743: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.743: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.743: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.743: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.743: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.743: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.744: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.744: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.744: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.744: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.744: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.744: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.745: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.745: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.745: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.745: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.745: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.745: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.745: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.745: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.746: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.746: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.746: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.746: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.746: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.746: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.747: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.747: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.747: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.747: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.747: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.747: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.748: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.748: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.748: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.748: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.748: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.748: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.749: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.749: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.749: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.749: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.749: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.749: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.749: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.749: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.750: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.750: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.750: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.750: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.750: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.750: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.751: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.751: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.751: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.751: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.751: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.751: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.752: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.752: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.752: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.752: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.752: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.752: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.752: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.752: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.753: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.753: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.753: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.753: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.753: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.753: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.754: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.754: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.754: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.754: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.754: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.754: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.755: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.755: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.755: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.755: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.755: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.755: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.755: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.755: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.756: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.756: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.756: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.756: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.756: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.756: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.757: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.757: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.757: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.757: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.757: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.757: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.758: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.758: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.758: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.758: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.758: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.758: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.758: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.758: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.759: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.759: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.759: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.759: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.759: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.759: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.760: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.760: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.760: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.760: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.760: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.760: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.761: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.761: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.761: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.761: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.761: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.761: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.761: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.761: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.762: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.762: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.762: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.762: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.762: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.762: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.763: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.763: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.763: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.763: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.763: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.763: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.764: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.764: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.764: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.764: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.764: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.764: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.764: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.764: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.765: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.765: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.765: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.765: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.765: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.765: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.766: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.766: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.766: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.766: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.766: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.766: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.767: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.767: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.767: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.767: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.767: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.767: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.767: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.767: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.768: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.768: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.768: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.768: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.768: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.768: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.769: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.769: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.769: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.769: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.769: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.769: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.770: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.770: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.770: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.770: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.770: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.770: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.771: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.771: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.771: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.771: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.771: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.771: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.771: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.771: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.772: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.772: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.772: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.772: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.772: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.772: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.773: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.773: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.773: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.773: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.773: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.773: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.774: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.774: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.774: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.774: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.774: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.774: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.774: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.774: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.775: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.775: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.775: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.775: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.775: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.775: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.776: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.776: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.776: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.776: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.776: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.776: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.777: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.777: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.777: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.777: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.777: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.777: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.778: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.778: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.778: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.778: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.778: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.778: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.778: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.778: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.779: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.779: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.779: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.779: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.779: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.779: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.780: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.780: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.780: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.780: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.780: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.781: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.781: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.781: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.781: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.781: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.781: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.781: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.782: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.782: Cleaning image 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.782: variance_after = 18 185s 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.782: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.782: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.782: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.782: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.783: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.783: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.783: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.783: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.783: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.783: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.784: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.784: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.784: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.784: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.784: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.784: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.784: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.785: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.785: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.785: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.785: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.785: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.785: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.785: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.786: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.786: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.786: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.786: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.786: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.786: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.787: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.787: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.787: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.787: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.787: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.787: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.788: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.788: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.788: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.788: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.788: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.788: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.788: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.788: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.789: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.789: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.789: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.789: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.789: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.789: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.790: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.790: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.790: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.790: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.790: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.790: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.791: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.791: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.791: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.791: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.791: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.791: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.791: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.791: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.792: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.792: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.792: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.792: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.792: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.792: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.793: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.793: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.793: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.793: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.793: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.793: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.794: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.794: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.794: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.794: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.794: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.794: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.794: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.794: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.795: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.795: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.795: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.795: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.795: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.795: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.796: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.796: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.796: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.796: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.796: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.796: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.797: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.797: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.797: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.797: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.797: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.797: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.797: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.797: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.798: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.798: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.798: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.798: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.798: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.798: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.799: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.799: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.799: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.799: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.799: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.799: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.800: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.800: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.800: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.800: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.800: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.800: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.800: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.800: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.801: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.801: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.801: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.801: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.801: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.801: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.802: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.802: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.802: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.802: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.802: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.802: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.803: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.803: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.803: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.803: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.803: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.803: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.803: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.803: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.804: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.804: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.804: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.804: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.804: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.804: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.805: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.805: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.805: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.805: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.805: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.805: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.806: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.806: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.806: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.806: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.806: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.806: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.806: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.806: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.807: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.807: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.807: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.807: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.807: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.807: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.808: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.808: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.808: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.808: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.808: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.808: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.808: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.808: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.809: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.809: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.809: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.809: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.809: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.809: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.810: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.810: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.810: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.810: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.810: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.810: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.811: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.811: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.811: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.811: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.811: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.811: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.812: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.812: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.812: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.812: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.812: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.812: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.812: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.812: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.813: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.813: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.813: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.813: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.813: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.813: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.813: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.813: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.814: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.814: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.814: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.814: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.814: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.814: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.814: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.814: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.815: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.815: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.815: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.815: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.815: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.815: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.816: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.816: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.816: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.816: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.816: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.816: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.816: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.816: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.817: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.817: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.817: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.817: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.817: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.817: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.818: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.818: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.818: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.818: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.818: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.818: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.819: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.819: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.819: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.819: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.819: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.819: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.820: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.820: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.820: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.820: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.820: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.820: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.820: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.820: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.821: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.821: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.821: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.821: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.821: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.821: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.822: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.822: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.822: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.822: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.822: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.822: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.823: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.823: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.823: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.823: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.823: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.823: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.824: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.824: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.824: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.824: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.824: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.824: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.825: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.825: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.825: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.825: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.825: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.825: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.825: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.825: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.826: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.826: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.826: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.826: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.826: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.826: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.826: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.827: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.827: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.827: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.827: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.827: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.828: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.828: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.828: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.828: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.828: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.828: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.829: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.829: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.829: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.829: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.829: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.829: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.829: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.829: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.830: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.830: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.830: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.830: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.830: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.830: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.831: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.831: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.831: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.831: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.831: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.831: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.832: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.832: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.832: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.832: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.832: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.832: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.832: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.832: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.833: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.833: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.833: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.833: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.833: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.833: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.834: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.834: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.834: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.834: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.834: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.834: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.835: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.835: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.835: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.835: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.835: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.835: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.835: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.835: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.836: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.836: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.836: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.836: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.836: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.836: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.837: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.837: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.837: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.837: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.837: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.837: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.838: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.838: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.838: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.838: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.838: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.838: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.838: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.838: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.839: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.839: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.839: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.839: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.839: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.839: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.840: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.840: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.840: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.840: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.840: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.840: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.841: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.841: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.841: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.841: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.841: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.841: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.842: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.842: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.842: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.842: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.842: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.842: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.842: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.842: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.843: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.843: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.843: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.843: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.843: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.843: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.844: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.844: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.844: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.844: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.844: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.844: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.845: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.845: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.845: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.845: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.845: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.845: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.845: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.845: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.846: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.846: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.846: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.846: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.846: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.846: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.847: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.847: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.847: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.847: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.847: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.847: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.847: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.847: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.848: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.848: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.848: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.848: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.848: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.848: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.849: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.849: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.849: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.849: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.849: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.849: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.850: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.850: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.850: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.850: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.850: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.850: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.850: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.851: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.851: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.851: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.851: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.851: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.851: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.851: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.852: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.852: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.852: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.852: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.852: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.852: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.852: Cleaning image 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.853: variance_after = 18 185s 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.853: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.853: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.853: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.853: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.853: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.853: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.853: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.853: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.854: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.854: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.854: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.854: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.854: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.854: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.854: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.854: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.855: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.855: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.855: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.855: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.855: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.855: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.856: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.856: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.856: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.856: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.856: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.856: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.857: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.857: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.857: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.857: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.857: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.857: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.857: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.857: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.858: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.858: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.858: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.858: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.858: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.858: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.859: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.859: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.859: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.859: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.859: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.859: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.860: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.860: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.860: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.860: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.860: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.860: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.861: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.861: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.861: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.861: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.861: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.861: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.861: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.861: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.862: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.862: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.862: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.862: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.862: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.862: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.863: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.863: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.863: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.863: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.863: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.863: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.863: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.863: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.864: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.864: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.864: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.864: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.864: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.864: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.865: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.865: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.865: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.865: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.865: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.865: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.865: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.866: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.866: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.866: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.866: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.866: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.866: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.866: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.866: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.867: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.867: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.867: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.867: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.867: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.867: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.868: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.868: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.868: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.868: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.868: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.868: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.868: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.868: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.869: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.869: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.869: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.869: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.869: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.869: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.869: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.870: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.870: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.870: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.870: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.870: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.870: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.871: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.871: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.871: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.871: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.871: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.871: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.871: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.871: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.872: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.872: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.872: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.872: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.872: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.872: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.873: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.873: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.873: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.873: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.873: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.873: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.873: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.873: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.874: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.874: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.874: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.874: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.874: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.874: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.875: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.875: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.875: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.875: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.875: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.875: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.876: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.876: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.876: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.876: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.876: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.876: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.876: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.876: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.877: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.877: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.877: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.877: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.877: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.877: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.878: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.878: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.878: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.878: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.878: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.878: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.879: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.879: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.879: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.879: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.879: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.879: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.880: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.880: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.880: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.880: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.880: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.880: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.880: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.880: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.881: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.881: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.881: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.881: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.881: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.881: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.882: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.882: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.882: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.882: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.882: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.882: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.883: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.883: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.883: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.883: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.883: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.883: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.883: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.883: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.884: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.884: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.884: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.884: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.884: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.884: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.885: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.885: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.885: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.885: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.885: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.885: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.886: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.886: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.886: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.886: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.886: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.886: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.887: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.887: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.887: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.887: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.887: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.887: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.887: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.887: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.888: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.888: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.888: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.888: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.888: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.888: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.889: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.889: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.889: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.889: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.889: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.889: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.890: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.890: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.890: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.890: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.890: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.890: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.890: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.890: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.891: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.891: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.891: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.891: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.891: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.891: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.892: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.892: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.892: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.892: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.892: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.892: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.893: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.893: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.893: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.893: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.893: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.893: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.894: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.894: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.894: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.894: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.894: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.894: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.894: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.894: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.895: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.895: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.895: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.895: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.895: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.895: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.896: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.896: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.896: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.896: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.896: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.896: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.896: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.897: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.897: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.897: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.897: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.897: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.897: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.897: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.898: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.898: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.898: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.898: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.898: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.898: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.899: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.899: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.899: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.899: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.899: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.899: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.900: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.900: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.900: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.900: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.900: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.900: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.900: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.900: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.901: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.901: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.901: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.901: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.901: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.901: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.901: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.901: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.902: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.902: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.902: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.902: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.902: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.902: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.902: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.902: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.903: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.903: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.903: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.903: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.903: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.903: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.903: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.903: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.904: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.904: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.904: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.904: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.904: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.904: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.905: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.905: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.905: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.905: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.905: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.905: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.906: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.906: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.906: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.906: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.906: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.906: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.906: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.906: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.907: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.907: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.907: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.907: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.907: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.907: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.908: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.908: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.908: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.908: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.908: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.908: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.908: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.908: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.909: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.909: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.909: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.909: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.909: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.909: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.910: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.910: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.910: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.910: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.910: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.910: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.911: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.911: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.911: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.911: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.911: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.911: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.911: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.911: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.912: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.912: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.912: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.912: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.912: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.912: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.913: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.913: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.913: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.913: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.913: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.913: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.914: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.914: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.914: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.914: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.914: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.914: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.915: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.915: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.915: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.915: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.915: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.915: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.915: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.915: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.916: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.916: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.916: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.916: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.916: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.916: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.917: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.917: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.917: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.917: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.917: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.917: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.918: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.918: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.918: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.918: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.918: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.918: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.918: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.918: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.919: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.919: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.919: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.919: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.919: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.920: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.920: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.920: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.920: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.920: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.920: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.920: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.921: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.921: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.921: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.921: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.921: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.921: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.921: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.921: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.922: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.922: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.922: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.922: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.922: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.922: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.923: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.923: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.923: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.923: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.923: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.923: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.924: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.924: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.924: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.924: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.924: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.924: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.924: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.924: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.925: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.925: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.925: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.925: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.925: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.925: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.926: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.926: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.926: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.926: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.926: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.926: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.927: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.927: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.927: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.927: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.927: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.928: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.928: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.928: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.928: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.928: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.928: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.928: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.929: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.929: Cleaning image 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.929: variance_after = 18 185s 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.929: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.929: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.929: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.929: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.930: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.930: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.930: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.930: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.930: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.930: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.931: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.931: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.931: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.931: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.931: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.931: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.931: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.932: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.932: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.932: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.932: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.932: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.932: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.932: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.932: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.933: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.933: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.933: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.933: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.933: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.933: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.934: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.934: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.934: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.934: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.934: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.934: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.934: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.934: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.935: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.935: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.935: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.935: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.935: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.935: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.936: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.936: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.936: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.936: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.936: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.936: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.936: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.936: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.937: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.937: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.937: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.937: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.937: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.937: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.938: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.938: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.938: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.938: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.938: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.938: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.938: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.938: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.939: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.939: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.939: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.939: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.939: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.939: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.940: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.940: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.940: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.940: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.940: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.940: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.941: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.941: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.941: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.941: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.941: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.941: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.941: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.941: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.942: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.942: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.942: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.942: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.942: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.942: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.943: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.943: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.943: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.943: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.943: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.943: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.944: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.944: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.944: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.944: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.944: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.944: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.944: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.945: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.945: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.945: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.945: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.945: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.945: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.945: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.946: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.946: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.946: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.946: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.946: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.946: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.947: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.947: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.947: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.947: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.947: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.947: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.948: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.948: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.948: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.948: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.948: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.948: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.948: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.948: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.949: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.949: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.949: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.949: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.949: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.949: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.950: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.950: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.950: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.950: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.950: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.950: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.951: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.951: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.951: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.951: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.951: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.951: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.952: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.952: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.952: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.952: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.952: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.952: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.952: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.952: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.953: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.953: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.953: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.953: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.953: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.953: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.954: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.954: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.954: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.954: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.954: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.954: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.955: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.955: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.955: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.955: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.955: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.955: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.955: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.955: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.956: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.956: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.956: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.956: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.956: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.956: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.957: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.957: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.957: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.957: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.957: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.957: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.958: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.958: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.958: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.958: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.958: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.958: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.958: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.958: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.959: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.959: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.959: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.959: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.959: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.959: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.960: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.960: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.960: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.960: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.960: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.960: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.961: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.961: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.961: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.961: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.961: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.961: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.961: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.962: [vfs7552] CAPTURE_NUM_STATES entering state 2 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.962: [vfs7552] REQUEST CHUNK entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.962: Sending vfs7552_read_image_chunk 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.962: [vfs7552] REQUEST CHUNK completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.962: [vfs7552] CAPTURE_NUM_STATES entering state 3 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.963: [vfs7552] CAPTURE_NUM_STATES entering state 4 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.963: Cleaning image 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.963: variance_after = 17 185s 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.963: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.963: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.963: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.963: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.963: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.963: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.963: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.963: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.964: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.964: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.964: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.964: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.964: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.964: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.965: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.965: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.965: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.965: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.965: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.965: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.965: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.965: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.966: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.966: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.966: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.966: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.966: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.966: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.967: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.967: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.967: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.967: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.967: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.967: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.968: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.968: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.968: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.968: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.968: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.968: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.968: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.968: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.969: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.969: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.969: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.969: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.969: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.969: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.970: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.970: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.970: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.970: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.970: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.970: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.971: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.971: Receiving 64 bytes 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.971: Got 6 bytes out of 64 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.971: [vfs7552] QUERY DATA READY completed successfully 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.971: [vfs7552] QUERY DATA READY entering state 0 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.971: Sending vfs7552_is_image_ready 185s (process:2469): libfprint-SSM-DEBUG: 00:01:17.971: [vfs7552] QUERY DATA READY entering state 1 185s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.971: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.972: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.972: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.972: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.972: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.972: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.972: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.973: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.973: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.973: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.973: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.973: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.973: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.974: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.974: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.974: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.974: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.974: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.974: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.974: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.974: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.975: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.975: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.975: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.975: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.975: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.975: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.976: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.976: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.976: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.976: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.976: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.976: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.977: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.977: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.977: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.977: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.977: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.977: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.977: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.977: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.978: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.978: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.978: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.978: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.978: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.978: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.979: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.979: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.979: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.979: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.979: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.979: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.980: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.980: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.980: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.980: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.980: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.980: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.980: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.980: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.981: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.981: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.981: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.981: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.981: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.981: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.982: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.982: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.982: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.982: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.982: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.982: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.983: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.983: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.983: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.983: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.983: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.983: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.983: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.983: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.984: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.984: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.984: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.984: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.984: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.984: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.985: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.985: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.985: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.985: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.985: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.985: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.986: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.986: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.986: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.986: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.986: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.986: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.986: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.986: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.987: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.987: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.987: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.987: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.987: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.987: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.988: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.988: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.988: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.988: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.988: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.988: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.989: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.989: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.989: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.989: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.989: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.989: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.989: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.989: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.990: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.990: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.990: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.990: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.990: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.990: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.991: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.991: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.991: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.991: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.991: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.991: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.992: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.992: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.992: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.992: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.992: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.992: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.993: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.993: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.993: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.993: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.993: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.993: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.993: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.993: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.994: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.994: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.994: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.994: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.994: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.994: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.995: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.995: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.995: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.995: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.995: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.995: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.995: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.996: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.996: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.996: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.996: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.996: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.996: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.996: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.997: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.997: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.997: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.997: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.997: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.997: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.997: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.998: variance_after = 16 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.998: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.998: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.998: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.998: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.998: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.998: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.998: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.998: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.999: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.999: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.999: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.999: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.999: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.999: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:17.999: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:17.999: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.000: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.000: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.000: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.000: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.000: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.000: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.001: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.001: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.001: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.001: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.001: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.001: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.002: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.002: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.002: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.002: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.002: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.002: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.002: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.002: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.003: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.003: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.003: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.003: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.003: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.003: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.004: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.004: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.004: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.004: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.004: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.004: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.005: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.005: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.005: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.005: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.005: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.005: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.006: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.006: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.006: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.006: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.006: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.006: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.006: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.006: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.007: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.007: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.007: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.007: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.007: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.007: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.008: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.008: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.008: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.008: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.008: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.008: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.009: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.009: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.009: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.009: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.009: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.009: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.009: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.009: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.010: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.010: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.010: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.010: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.010: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.010: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.011: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.011: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.011: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.011: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.011: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.011: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.012: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.012: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.012: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.012: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.012: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.012: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.013: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.013: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.013: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.013: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.013: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.013: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.013: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.013: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.014: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.014: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.014: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.014: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.014: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.014: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.015: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.015: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.015: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.015: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.015: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.015: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.016: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.016: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.016: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.016: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.016: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.016: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.016: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.016: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.017: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.017: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.017: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.017: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.017: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.017: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.018: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.018: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.018: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.018: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.018: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.018: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.019: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.019: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.019: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.019: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.019: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.019: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.019: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.019: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.020: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.020: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.020: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.020: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.020: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.020: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.021: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.021: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.021: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.021: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.021: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.021: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.022: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.022: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.022: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.022: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.022: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.022: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.023: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.023: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.023: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.023: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.023: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.023: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.023: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.023: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.024: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.024: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.024: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.024: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.024: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.024: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.025: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.025: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.025: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.025: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.025: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.025: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.026: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.026: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.026: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.026: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.026: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.026: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.026: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.026: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.027: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.027: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.027: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.027: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.027: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.027: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.028: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.028: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.028: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.028: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.028: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.028: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.029: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.029: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.029: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.029: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.029: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.029: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.029: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.029: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.030: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.030: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.030: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.030: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.030: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.030: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.031: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.031: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.031: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.031: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.031: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.031: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.031: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.031: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.031: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.031: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.032: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.032: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.032: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.032: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.032: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.032: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.032: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.033: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.033: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.033: variance_after = 17 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.033: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.033: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.033: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.033: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.034: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.034: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.034: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.034: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.034: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.034: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.035: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.035: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.035: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.035: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.035: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.035: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.036: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.036: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.036: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.036: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.036: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.036: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.036: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.036: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.037: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.037: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.037: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.037: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.037: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.037: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.038: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.038: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.038: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.038: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.038: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.038: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.039: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.039: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.039: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.039: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.039: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.039: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.039: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.039: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.040: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.040: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.040: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.040: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.040: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.040: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.041: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.041: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.041: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.041: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.041: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.041: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.042: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.042: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.042: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.042: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.042: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.042: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.042: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.042: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.043: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.043: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.043: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.043: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.043: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.043: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.044: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.044: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.044: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.044: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.044: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.044: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.045: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.045: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.045: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.045: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.045: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.045: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.045: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.045: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.046: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.046: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.046: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.046: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.046: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.046: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.047: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.047: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.047: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.047: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.047: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.047: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.048: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.048: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.048: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.048: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.048: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.048: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.049: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.049: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.049: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.049: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.049: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.049: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.049: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.049: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.050: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.050: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.050: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.050: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.050: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.050: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.051: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.051: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.051: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.051: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.051: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.051: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.052: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.052: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.052: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.052: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.052: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.052: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.052: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.052: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.053: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.053: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.053: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.053: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.053: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.053: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.054: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.054: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.054: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.054: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.054: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.054: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.055: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.055: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.055: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.055: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.055: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.055: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.055: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.055: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.056: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.056: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.056: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.056: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.056: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.056: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.057: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.057: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.057: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.057: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.057: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.057: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.058: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.058: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.058: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.058: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.058: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.058: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.058: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.058: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.059: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.059: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.059: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.059: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.059: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.059: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.060: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.060: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.060: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.060: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.060: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.060: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.061: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.061: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.061: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.061: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.061: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.061: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.061: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.062: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.062: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.062: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.062: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.062: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.062: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.062: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.063: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.063: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.063: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.063: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.063: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.063: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.064: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.064: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.064: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.064: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.064: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.064: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.065: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.065: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.065: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.065: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.065: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.065: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.065: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.065: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.066: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.066: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.066: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.066: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.066: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.067: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.067: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.067: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.067: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.067: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.067: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.067: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.068: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.068: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.068: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.068: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.068: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.068: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.068: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.068: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.069: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.069: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.069: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.069: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.069: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.069: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.070: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.070: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.070: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.070: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.070: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.071: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.071: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.071: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.071: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.071: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.071: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.071: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.072: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.072: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.072: variance_after = 17 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.072: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.072: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.072: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.072: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.073: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.073: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.073: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.073: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.073: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.073: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.074: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.074: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.074: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.074: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.074: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.074: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.074: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.074: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.075: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.075: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.075: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.075: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.075: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.075: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.076: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.076: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.076: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.076: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.076: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.076: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.077: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.077: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.077: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.077: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.077: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.077: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.078: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.078: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.078: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.078: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.078: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.078: Sending vfs7552_is_image_ready 186s Executing: libfprint-2/driver-vfs7552.test 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.078: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.078: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.079: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.079: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.079: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.079: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.079: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.079: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.080: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.080: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.080: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.080: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.080: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.080: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.081: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.081: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.081: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.081: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.081: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.081: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.082: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.082: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.082: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.082: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.082: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.082: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.082: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.082: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.083: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.083: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.083: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.083: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.083: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.083: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.084: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.084: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.084: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.084: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.084: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.084: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.084: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.084: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.085: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.085: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.085: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.085: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.085: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.085: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.085: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.086: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.086: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.086: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.086: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.086: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.087: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.087: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.087: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.087: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.087: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.087: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.088: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.088: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.088: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.088: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.088: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.088: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.088: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.088: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.089: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.089: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.089: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.089: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.089: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.089: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.090: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.090: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.090: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.090: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.090: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.090: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.091: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.091: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.091: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.091: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.091: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.091: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.091: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.091: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.092: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.092: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.092: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.092: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.092: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.092: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.093: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.093: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.093: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.093: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.093: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.093: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.094: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.094: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.094: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.094: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.094: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.094: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.094: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.094: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.095: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.095: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.095: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.095: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.095: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.095: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.096: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.096: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.096: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.096: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.096: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.096: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.097: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.097: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.097: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.097: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.097: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.097: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.097: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.097: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.098: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.098: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.098: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.098: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.098: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.098: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.098: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.098: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.099: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.099: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.099: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.099: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.099: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.099: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.099: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.099: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.100: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.100: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.100: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.100: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.100: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.100: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.100: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.100: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.101: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.101: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.101: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.101: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.101: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.101: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.102: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.102: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.102: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.102: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.102: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.102: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.103: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.103: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.103: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.103: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.103: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.103: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.103: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.103: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.104: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.104: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.104: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.104: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.104: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.104: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.105: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.105: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.105: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.105: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.105: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.105: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.106: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.106: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.106: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.106: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.106: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.106: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.106: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.106: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.107: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.107: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.107: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.107: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.107: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.107: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.108: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.108: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.108: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.108: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.108: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.108: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.109: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.109: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.109: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.109: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.109: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.109: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.110: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.110: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.110: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.110: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.110: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.110: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.110: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.110: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.111: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.111: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.111: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.111: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.111: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.111: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.112: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.112: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.112: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.112: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.112: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.112: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.113: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.113: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.113: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.113: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.113: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.113: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.113: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.113: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.114: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.114: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.114: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.114: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.114: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.115: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.115: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.115: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.115: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.115: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.115: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.115: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.116: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.116: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.116: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.116: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.116: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.116: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.116: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.116: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.116: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.117: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.117: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.117: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.117: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.117: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.117: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.117: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.117: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.118: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.118: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.118: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.118: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.119: variance_after = 17 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.119: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.119: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.119: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.119: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.119: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.120: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.120: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.120: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.120: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.120: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.121: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.121: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.121: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.121: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.121: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.121: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.121: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.121: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.122: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.122: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.122: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.122: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.122: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.122: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.122: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.122: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.123: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.123: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.123: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.123: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.123: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.123: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.123: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.123: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.124: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.124: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.124: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.124: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.124: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.124: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.124: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.124: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.125: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.125: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.125: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.125: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.125: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.125: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.125: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.126: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.126: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.126: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.126: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.126: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.127: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.127: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.127: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.127: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.127: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.127: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.128: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.128: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.128: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.128: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.128: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.128: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.128: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.128: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.129: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.129: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.129: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.129: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.129: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.129: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.130: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.130: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.130: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.130: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.130: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.130: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.131: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.131: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.131: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.131: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.131: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.131: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.131: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.131: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.132: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.132: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.132: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.132: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.132: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.132: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.133: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.133: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.133: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.133: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.133: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.133: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.134: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.134: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.134: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.134: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.134: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.134: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.134: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.134: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.135: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.135: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.135: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.135: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.135: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.135: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.136: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.136: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.136: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.136: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.136: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.136: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.137: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.137: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.137: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.137: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.137: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.137: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.137: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.137: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.138: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.138: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.138: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.138: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.138: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.138: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.139: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.139: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.139: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.139: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.139: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.139: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.140: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.140: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.140: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.140: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.140: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.140: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.140: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.140: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.141: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.141: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.141: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.141: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.141: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.141: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.141: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.142: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.142: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.142: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.142: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.142: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.143: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.143: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.143: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.143: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.143: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.143: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.143: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.143: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.144: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.144: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.144: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.144: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.144: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.144: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.145: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.145: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.145: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.145: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.145: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.145: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.146: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.146: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.146: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.146: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.146: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.146: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.146: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.146: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.147: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.147: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.147: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.147: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.147: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.147: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.148: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.148: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.148: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.148: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.148: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.148: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.149: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.149: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.149: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.149: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.149: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.149: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.150: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.150: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.150: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.150: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.150: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.150: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.151: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.151: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.151: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.151: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.151: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.151: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.151: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.151: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.152: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.152: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.152: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.152: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.152: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.152: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.153: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.153: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.153: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.153: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.153: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.153: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.154: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.154: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.154: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.154: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.154: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.154: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.154: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.154: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.155: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.155: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.155: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.155: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.155: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.155: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.156: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.156: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.156: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.156: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.156: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.156: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.157: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.157: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.157: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.157: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.157: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.157: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.157: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.157: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.158: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.158: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.158: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.158: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.158: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.158: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.159: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.159: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.159: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.159: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.159: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.159: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.160: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.160: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.160: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.160: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.160: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.160: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.160: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.160: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.161: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.161: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.161: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.161: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.161: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.161: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.162: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.162: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.162: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.162: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.162: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.162: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.163: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.163: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.163: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.163: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.163: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.163: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.163: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.163: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.164: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.164: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.164: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.164: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.164: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.164: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.165: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.165: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.165: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.165: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.165: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.165: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.166: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.166: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.166: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.166: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.166: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.166: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.166: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.166: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.167: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.167: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.167: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.167: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.167: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.167: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.168: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.168: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.168: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.168: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.168: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.168: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.169: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.169: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.169: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.169: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.169: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.169: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.170: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.170: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.170: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.170: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.170: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.170: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.170: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.170: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.171: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.171: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.171: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.171: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.171: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.171: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.172: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.172: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.172: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.172: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.172: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.172: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.172: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.172: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.173: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.173: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.173: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.173: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.173: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.173: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.174: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.174: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.174: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.174: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.174: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.174: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.175: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.175: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.175: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.175: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.175: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.175: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.175: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.175: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.176: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.176: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.176: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.176: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.176: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.176: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.177: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.177: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.177: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.177: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.177: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.177: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.178: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.178: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.178: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.178: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.178: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.178: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.178: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.178: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.179: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.179: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.179: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.179: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.179: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.179: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.180: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.180: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.180: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.180: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.180: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.180: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.181: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.181: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.181: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.181: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.181: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.181: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.182: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.182: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.182: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.182: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.182: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.182: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.182: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.182: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.183: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.183: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.183: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.183: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.183: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.183: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.184: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.184: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.184: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.184: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.184: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.184: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.185: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.185: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.185: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.185: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.185: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.185: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.185: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.185: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.186: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.186: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.186: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.186: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.186: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.186: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.187: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.187: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.187: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.187: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.187: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.187: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.188: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.188: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.188: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.188: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.188: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.188: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.189: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.189: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.189: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.189: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.189: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.189: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.189: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.189: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.190: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.190: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.190: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.190: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.190: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.190: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.191: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.191: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.191: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.191: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.191: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.191: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.192: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.192: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.192: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.192: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.192: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.192: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.192: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.192: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.193: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.193: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.193: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.193: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.193: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.193: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.194: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.194: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.194: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.194: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.194: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.194: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.195: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.195: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.195: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.195: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.195: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.195: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.195: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.195: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.196: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.196: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.196: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.196: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.196: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.196: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.197: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.197: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.197: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.197: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.197: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.197: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.198: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.198: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.198: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.198: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.198: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.198: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.198: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.198: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.199: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.199: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.199: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.199: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.199: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.199: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.200: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.200: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.200: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.200: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.200: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.200: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.201: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.201: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.201: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.201: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.201: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.201: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.202: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.202: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.202: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.202: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.202: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.202: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.202: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.202: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.203: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.203: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.203: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.203: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.203: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.203: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.204: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.204: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.204: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.204: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.204: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.204: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.205: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.205: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.205: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.205: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.205: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.205: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.205: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.205: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.206: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.206: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.206: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.206: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.206: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.206: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.207: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.207: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.207: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.207: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.207: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.207: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.208: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.208: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.208: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.208: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.208: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.208: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.208: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.208: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.209: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.209: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.209: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.209: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.209: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.209: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.210: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.210: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.210: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.210: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.210: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.210: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.211: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.211: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.211: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.211: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.211: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.211: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.211: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.211: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.212: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.212: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.212: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.212: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.212: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.212: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.213: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.213: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.213: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.213: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.213: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.213: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.214: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.214: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.214: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.214: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.214: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.214: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.214: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.214: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.215: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.215: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.215: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.215: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.215: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.215: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.216: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.216: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.216: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.216: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.216: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.216: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.217: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.217: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.217: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.217: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.217: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.217: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.218: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.218: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.218: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.218: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.218: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.218: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.218: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.218: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.219: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.219: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.219: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.219: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.219: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.219: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.220: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.220: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.220: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.220: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.220: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.220: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.221: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.221: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.221: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.221: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.221: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.221: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.221: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.222: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.222: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.222: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.222: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.222: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.222: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.222: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.223: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.223: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.223: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.223: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.223: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.223: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.224: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.224: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.224: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.224: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.224: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.224: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.225: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.225: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.225: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.225: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.225: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.225: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.226: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.226: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.226: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.226: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.226: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.226: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.226: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.226: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.227: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.227: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.227: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.227: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.227: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.227: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.228: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.228: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.228: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.228: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.228: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.228: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.229: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.229: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.229: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.229: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.229: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.229: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.230: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.230: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.230: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.230: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.230: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.230: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.230: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.230: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.231: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.231: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.231: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.231: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.231: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.231: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.232: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.232: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.232: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.232: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.232: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.233: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.233: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.233: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.233: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.233: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.233: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.233: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.234: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.234: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.234: variance_after = 20 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.234: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.234: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.234: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.234: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.235: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.235: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.235: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.235: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.235: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.235: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.236: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.236: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.236: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.236: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.236: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.236: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.236: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.236: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.237: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.237: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.237: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.237: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.237: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.237: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.238: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.238: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.238: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.238: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.238: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.238: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.239: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.239: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.239: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.239: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.239: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.239: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.240: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.240: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.240: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.240: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.240: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.240: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.240: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.240: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.241: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.241: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.241: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.241: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.241: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.241: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.242: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.242: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.242: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.242: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.242: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.242: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.243: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.243: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.243: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.243: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.243: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.243: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.243: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.243: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.244: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.244: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.244: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.244: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.244: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.244: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.245: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.245: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.245: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.245: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.245: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.245: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.246: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.246: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.246: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.246: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.246: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.246: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.246: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.246: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.247: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.247: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.247: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.247: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.247: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.247: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.248: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.248: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.248: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.248: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.248: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.248: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.249: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.249: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.249: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.249: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.249: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.249: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.249: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.249: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.250: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.250: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.250: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.250: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.250: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.250: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.251: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.251: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.251: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.251: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.251: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.251: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.252: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.252: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.252: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.252: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.252: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.252: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.252: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.252: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.253: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.253: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.253: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.253: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.253: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.253: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.253: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.254: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.254: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.254: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.254: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.254: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.255: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.255: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.255: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.255: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.255: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.255: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.255: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.255: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.256: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.256: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.256: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.256: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.256: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.256: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.257: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.257: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.257: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.257: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.257: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.257: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.258: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.258: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.258: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.258: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.258: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.258: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.258: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.258: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.259: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.259: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.259: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.259: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.259: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.259: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.260: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.260: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.260: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.260: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.260: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.260: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.261: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.261: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.261: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.261: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.261: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.261: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.261: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.261: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.262: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.262: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.262: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.262: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.262: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.262: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.263: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.263: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.263: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.263: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.263: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.263: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.264: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.264: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.264: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.264: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.264: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.264: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.264: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.264: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.265: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.265: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.265: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.265: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.265: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.265: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.266: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.266: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.266: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.266: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.266: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.266: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.267: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.267: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.267: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.267: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.267: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.267: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.268: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.268: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.268: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.268: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.268: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.268: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.268: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.268: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.269: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.269: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.269: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.269: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.269: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.269: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.270: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.270: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.270: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.270: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.270: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.270: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.270: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.270: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.271: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.271: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.271: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.271: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.271: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.271: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.272: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.272: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.272: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.272: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.272: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.272: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.273: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.273: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.273: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.273: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.273: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.273: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.273: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.273: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.274: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.274: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.274: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.274: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.274: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.274: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.274: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.274: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.275: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.275: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.275: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.275: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.275: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.275: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.275: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.275: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.276: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.276: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.276: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.276: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.276: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.276: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.276: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.276: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.277: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.277: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.277: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.277: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.277: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.277: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.277: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.278: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.278: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.278: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.278: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.278: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.279: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.279: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.279: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.279: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.279: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.279: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.279: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.279: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.280: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.280: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.280: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.280: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.280: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.280: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.281: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.281: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.281: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.281: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.281: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.281: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.282: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.282: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.282: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.282: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.282: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.282: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.282: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.282: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.283: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.283: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.283: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.283: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.283: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.283: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.284: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.284: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.284: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.284: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.284: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.284: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.285: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.285: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.285: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.285: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.285: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.285: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.285: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.286: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.286: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.286: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.286: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.286: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.286: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.286: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.287: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.287: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.287: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.287: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.287: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.287: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.288: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.288: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.288: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.288: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.288: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.288: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.289: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.289: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.289: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.289: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.289: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.289: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.289: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.289: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.290: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.290: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.290: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.290: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.290: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.290: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.291: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.291: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.291: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.291: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.291: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.292: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.292: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.292: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.292: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.292: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.292: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.292: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.293: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.293: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.293: variance_after = 17 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.293: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.293: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.293: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.293: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.293: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.293: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.293: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.293: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.294: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.294: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.294: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.294: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.294: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.294: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.295: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.295: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.295: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.295: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.295: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.295: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.295: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.295: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.296: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.296: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.296: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.296: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.296: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.296: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.297: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.297: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.297: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.297: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.297: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.297: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.298: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.298: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.298: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.298: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.298: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.298: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.298: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.298: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.299: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.299: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.299: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.299: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.299: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.299: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.300: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.300: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.300: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.300: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.300: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.300: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.301: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.301: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.301: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.301: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.301: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.301: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.301: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.302: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.302: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.302: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.302: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.302: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.302: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.302: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.303: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.303: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.303: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.303: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.303: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.303: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.304: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.304: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.304: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.304: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.304: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.304: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.304: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.304: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.305: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.305: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.305: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.305: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.305: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.305: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.306: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.306: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.306: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.306: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.306: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.306: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.307: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.307: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.307: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.307: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.307: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.307: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.308: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.308: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.308: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.308: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.308: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.308: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.308: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.308: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.309: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.309: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.309: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.309: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.309: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.309: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.310: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.310: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.310: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.310: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.310: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.310: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.311: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.311: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.311: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.311: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.311: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.311: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.311: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.311: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.312: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.312: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.312: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.312: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.312: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.312: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.313: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.313: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.313: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.313: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.313: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.313: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.314: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.314: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.314: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.314: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.314: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.314: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.314: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.314: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.315: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.315: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.315: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.315: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.315: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.315: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.316: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.316: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.316: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.316: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.316: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.316: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.317: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.317: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.317: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.317: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.317: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.317: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.317: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.317: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.318: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.318: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.318: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.318: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.318: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.318: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.319: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.319: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.319: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.319: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.319: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.319: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.319: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.319: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.320: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.320: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.320: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.320: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.320: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.320: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.321: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.321: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.321: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.321: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.321: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.321: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.322: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.322: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.322: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.322: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.322: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.322: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.323: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.323: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.323: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.323: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.323: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.323: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.323: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.323: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.324: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.324: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.324: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.324: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.324: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.324: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.325: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.325: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.325: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.325: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.325: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.325: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.326: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.326: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.326: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.326: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.326: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.326: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.326: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.326: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.327: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.327: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.327: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.327: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.327: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.327: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.328: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.328: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.328: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.328: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.328: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.328: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.329: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.329: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.329: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.329: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.329: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.329: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.329: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.329: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.330: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.330: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.330: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.330: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.330: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.330: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.330: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.331: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.331: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.331: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.331: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.331: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.331: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.331: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.331: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.332: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.332: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.332: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.332: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.332: variance_after = 17 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.332: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.332: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.333: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.333: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.333: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.333: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.333: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.333: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.333: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.333: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.334: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.334: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.334: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.334: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.334: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.334: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.335: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.335: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.335: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.335: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.335: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.335: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.336: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.336: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.336: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.336: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.336: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.336: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.336: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.336: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.337: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.337: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.337: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.337: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.337: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.337: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.338: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.338: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.338: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.338: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.338: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.338: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.339: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.339: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.339: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.339: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.339: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.339: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.339: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.339: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.340: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.340: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.340: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.340: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.340: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.340: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.341: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.341: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.341: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.341: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.341: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.341: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.342: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.342: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.342: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.342: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.342: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.342: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.342: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.342: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.343: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.343: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.343: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.343: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.343: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.343: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.344: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.344: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.344: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.344: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.344: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.344: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.345: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.345: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.345: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.345: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.345: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.345: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.345: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.345: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.346: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.346: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.346: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.346: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.346: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.346: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.347: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.347: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.347: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.347: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.347: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.347: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.348: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.348: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.348: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.348: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.348: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.348: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.348: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.348: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.349: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.349: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.349: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.349: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.349: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.349: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.350: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.350: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.350: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.350: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.350: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.350: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.351: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.351: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.351: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.351: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.351: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.351: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.351: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.351: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.352: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.352: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.352: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.352: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.352: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.352: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.353: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.353: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.353: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.353: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.353: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.353: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.354: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.354: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.354: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.354: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.354: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.354: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.354: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.354: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.355: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.355: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.355: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.355: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.355: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.355: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.356: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.356: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.356: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.356: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.356: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.356: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.357: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.357: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.357: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.357: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.357: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.357: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.357: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.357: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.358: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.358: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.358: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.358: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.358: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.358: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.359: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.359: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.359: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.359: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.359: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.359: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.360: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.360: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.360: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.360: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.360: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.360: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.360: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.360: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.361: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.361: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.361: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.361: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.361: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.361: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.362: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.362: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.362: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.362: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.362: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.362: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.363: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.363: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.363: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.363: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.363: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.363: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.363: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.363: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.364: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.364: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.364: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.364: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.364: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.364: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.365: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.365: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.365: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.365: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.365: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.365: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.366: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.366: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.366: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.366: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.366: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.366: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.366: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.366: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.367: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.367: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.367: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.367: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.367: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.367: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.367: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.368: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.368: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.368: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.368: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.368: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.368: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.368: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.368: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.369: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.369: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.369: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.369: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.369: variance_after = 17 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.369: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.369: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.370: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.370: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.370: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.370: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.370: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.370: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.370: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.370: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.371: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.371: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.371: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.371: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.371: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.371: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.372: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.372: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.372: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.372: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.372: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.372: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.373: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.373: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.373: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.373: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.373: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.373: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.373: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.373: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.374: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.374: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.374: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.374: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.374: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.374: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.375: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.375: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.375: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.375: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.375: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.375: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.376: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.376: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.376: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.376: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.376: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.376: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.376: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.376: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.377: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.377: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.377: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.377: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.377: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.377: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.378: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.378: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.378: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.378: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.378: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.378: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.379: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.379: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.379: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.379: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.379: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.379: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.379: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.379: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.380: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.380: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.380: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.380: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.380: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.380: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.381: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.381: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.381: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.381: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.381: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.381: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.382: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.382: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.382: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.382: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.382: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.382: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.383: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.383: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.383: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.383: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.383: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.383: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.383: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.383: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.384: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.384: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.384: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.384: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.384: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.384: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.385: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.385: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.385: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.385: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.385: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.385: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.386: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.386: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.386: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.386: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.386: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.386: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.386: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.386: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.387: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.387: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.387: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.387: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.387: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.387: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.388: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.388: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.388: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.388: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.388: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.388: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.389: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.389: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.389: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.389: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.389: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.389: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.389: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.389: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.390: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.390: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.390: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.390: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.390: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.390: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.391: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.391: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.391: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.391: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.391: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.391: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.392: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.392: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.392: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.392: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.392: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.392: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.392: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.392: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.393: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.393: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.393: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.393: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.393: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.393: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.394: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.394: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.394: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.394: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.394: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.394: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.395: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.395: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.395: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.395: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.395: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.395: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.395: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.395: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.396: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.396: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.396: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.396: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.396: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.396: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.397: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.397: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.397: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.397: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.397: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.397: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.398: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.398: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.398: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.398: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.398: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.398: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.399: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.399: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.399: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.399: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.399: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.399: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.399: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.399: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.400: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.400: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.400: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.400: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.400: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.400: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.401: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.401: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.401: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.401: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.401: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.402: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.402: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.402: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.402: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.402: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.402: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.402: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.403: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.403: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.403: variance_after = 17 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.403: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.403: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.403: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.403: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.403: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.403: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.403: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.403: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.404: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.404: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.404: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.404: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.404: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.404: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.405: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.405: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.405: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.405: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.405: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.405: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.405: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.405: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.406: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.406: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.406: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.406: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.406: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.406: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.407: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.407: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.407: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.407: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.407: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.407: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.408: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.408: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.408: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.408: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.408: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.408: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.408: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.408: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.409: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.409: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.409: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.409: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.409: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.409: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.410: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.410: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.410: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.410: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.410: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.410: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.411: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.411: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.411: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.411: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.411: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.411: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.411: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.411: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.412: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.412: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.412: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.412: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.412: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.412: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.413: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.413: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.413: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.413: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.413: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.413: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.414: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.414: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.414: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.414: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.414: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.414: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.415: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.415: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.415: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.415: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.415: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.415: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.415: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.415: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.416: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.416: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.416: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.416: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.416: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.416: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.417: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.417: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.417: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.417: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.417: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.417: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.417: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.417: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.418: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.418: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.418: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.418: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.418: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.418: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.419: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.419: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.419: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.419: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.419: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.419: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.420: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.420: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.420: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.420: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.420: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.420: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.420: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.420: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.421: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.421: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.421: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.421: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.421: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.421: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.422: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.422: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.422: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.422: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.422: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.422: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.423: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.423: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.423: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.423: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.423: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.423: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.424: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.424: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.424: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.424: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.424: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.424: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.424: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.424: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.425: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.425: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.425: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.425: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.425: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.425: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.426: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.426: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.426: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.426: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.426: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.426: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.427: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.427: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.427: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.427: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.427: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.427: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.428: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.428: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.428: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.428: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.428: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.428: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.428: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.428: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.429: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.429: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.429: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.429: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.429: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.429: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.430: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.430: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.430: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.430: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.430: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.430: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.431: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.431: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.431: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.431: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.431: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.431: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.431: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.431: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.432: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.432: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.432: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.432: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.432: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.432: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.433: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.433: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.433: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.433: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.433: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.433: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.434: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.434: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.434: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.434: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.434: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.434: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.435: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.435: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.435: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.435: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.435: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.435: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.435: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.435: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.436: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.436: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.436: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.436: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.436: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.436: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.437: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.437: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.437: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.437: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.437: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.437: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.437: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.438: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.438: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.438: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.438: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.438: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.438: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.438: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.439: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.439: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.439: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.439: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.439: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.440: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.440: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.440: variance_after = 16 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.440: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.440: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.440: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.440: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.440: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.440: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.440: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.440: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.441: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.441: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.441: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.441: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.441: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.441: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.441: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.442: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.442: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.442: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.442: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.442: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.442: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.442: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.442: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.443: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.443: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.443: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.443: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.443: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.443: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.443: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.444: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.444: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.444: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.444: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.444: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.444: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.444: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.445: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.445: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.445: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.445: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.445: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.445: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.446: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.446: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.446: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.446: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.446: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.446: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.446: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.447: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.447: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.447: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.447: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.447: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.447: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.447: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.447: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.448: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.448: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.448: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.448: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.448: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.448: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.448: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.449: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.449: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.449: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.449: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.449: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.449: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.450: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.450: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.450: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.450: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.450: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.450: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.450: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.451: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.451: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.451: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.451: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.451: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.451: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.451: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.452: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.452: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.452: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.452: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.452: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.452: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.452: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.453: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.453: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.453: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.453: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.453: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.454: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.454: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.454: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.454: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.454: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.454: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.454: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.454: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.454: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.454: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.455: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.455: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.455: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.455: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.455: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.455: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.455: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.456: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.456: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.456: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.456: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.456: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.456: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.457: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.457: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.457: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.457: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.457: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.457: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.457: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.457: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.458: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.458: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.458: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.458: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.458: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.458: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.458: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.459: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.459: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.459: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.459: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.459: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.459: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.460: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.460: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.460: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.460: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.460: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.460: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.460: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.461: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.461: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.461: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.461: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.461: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.461: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.461: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.461: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.462: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.462: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.462: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.462: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.462: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.462: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.462: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.463: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.463: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.463: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.463: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.463: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.463: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.463: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.464: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.464: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.464: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.464: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.464: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.464: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.465: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.465: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.465: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.465: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.465: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.465: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.465: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.465: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.466: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.466: variance_after = 17 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.466: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.466: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.466: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.466: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.466: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.467: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.467: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.467: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.467: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.467: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.467: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.467: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.467: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.468: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.468: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.468: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.468: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.468: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.468: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.469: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.469: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.469: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.469: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.469: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.469: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.470: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.470: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.470: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.470: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.470: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.470: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.471: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.471: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.471: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.471: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.471: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.471: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.471: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.471: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.471: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.471: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.472: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.472: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.472: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.472: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.472: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.472: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.473: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.473: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.473: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.473: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.473: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.473: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.473: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.474: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.474: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.474: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.474: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.474: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.474: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.475: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.475: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.475: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.475: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.475: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.475: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.475: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.476: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.476: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.476: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.476: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.476: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.476: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.476: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.476: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.477: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.477: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.477: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.477: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.477: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.477: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.478: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.478: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.478: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.478: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.478: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.478: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.479: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.479: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.479: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.479: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.479: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.479: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.480: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.480: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.480: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.480: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.480: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.480: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.480: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.480: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.481: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.481: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.481: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.481: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.481: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.481: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.482: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.482: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.482: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.482: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.482: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.482: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.483: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.483: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.483: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.483: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.483: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.483: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.483: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.484: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.484: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.484: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.484: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.484: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.484: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.484: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.485: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.485: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.485: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.485: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.485: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.485: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.485: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.485: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.486: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.486: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.486: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.486: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.486: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.486: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.487: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.487: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.487: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.487: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.487: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.487: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.487: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.487: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.488: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.488: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.488: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.488: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.488: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.488: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.489: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.489: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.489: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.489: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.489: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.489: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.489: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.490: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.490: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.490: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.490: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.490: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.490: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.490: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.490: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.491: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.491: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.491: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.491: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.491: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.491: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.491: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.492: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.492: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.492: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.492: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.492: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.492: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.493: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.493: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.493: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.493: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.493: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.493: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.493: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.493: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.493: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.493: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.494: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.494: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.494: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.494: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.494: variance_after = 16 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.494: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.494: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.494: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.494: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.495: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.495: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.495: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.495: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.495: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.495: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.495: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.496: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.496: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.496: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.496: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.496: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.496: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.497: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.497: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.497: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.497: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.497: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.497: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.497: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.497: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.498: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.498: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.498: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.498: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.498: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.498: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.498: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.498: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.499: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.499: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.499: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.499: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.499: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.499: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.499: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.499: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.499: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.499: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.500: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.500: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.500: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.500: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.500: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.500: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.501: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.501: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.501: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.501: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.501: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.501: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.501: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.501: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.502: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.502: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.502: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.502: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.502: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.502: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.502: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.503: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.503: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.503: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.503: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.503: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.503: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.504: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.504: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.504: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.504: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.504: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.504: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.504: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.504: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.505: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.505: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.505: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.505: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.505: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.505: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.505: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.506: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.506: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.506: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.506: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.506: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.506: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.506: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.507: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.507: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.507: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.507: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.507: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.507: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.508: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.508: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.508: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.508: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.508: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.508: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.508: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.509: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.509: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.509: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.509: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.509: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.509: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.510: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.510: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.510: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.510: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.510: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.510: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.510: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.511: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.511: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.511: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.511: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.511: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.511: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.511: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.511: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.512: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.512: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.512: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.512: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.512: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.512: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.512: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.513: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.513: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.513: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.513: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.513: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.513: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.514: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.514: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.514: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.514: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.514: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.514: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.514: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.515: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.515: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.515: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.515: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.515: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.515: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.515: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.515: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.516: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.516: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.516: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.516: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.516: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.516: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.517: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.517: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.517: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.517: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.517: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.517: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.517: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.517: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.518: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.518: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.518: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.518: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.518: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.518: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.519: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.519: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.519: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.519: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.519: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.519: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.519: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.519: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.519: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.520: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.520: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.520: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.520: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.520: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.520: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.520: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.520: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.521: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.521: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.521: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.521: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.521: variance_after = 2168 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.521: [vfs7552] CAPTURE_NUM_STATES completed successfully 186s (process:2469): libfprint-device-DEBUG: 00:01:18.521: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:2469): libfprint-image_device-DEBUG: 00:01:18.521: Image device reported finger status: on 186s (process:2469): libfprint-image_device-DEBUG: 00:01:18.521: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.571: changing to 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.571: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.571: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.571: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.571: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.572: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.572: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.572: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.572: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.573: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.573: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.573: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.573: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.573: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.573: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.573: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.573: variance_after = 2082 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.573: [vfs7552] CAPTURE_NUM_STATES completed successfully 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.573: Image captured 186s (process:2469): libfprint-image_device-DEBUG: 00:01:18.573: Image device captured an image 186s (process:2469): libfprint-image_device-DEBUG: 00:01:18.574: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 186s (process:2469): libfprint-device-DEBUG: 00:01:18.574: Device reported finger status change: FP_FINGER_STATUS_PRESENT 186s (process:2469): libfprint-image-DEBUG: 00:01:18.596: Minutiae scan completed in 0.022571 secs 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.623: changing to 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.623: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.623: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.624: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.624: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.624: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.624: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.624: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.625: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.625: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.625: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.625: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.626: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.626: variance_after = 2003 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.626: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.626: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.626: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.626: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.626: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.626: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.627: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.627: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.627: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.627: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.627: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.627: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.628: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.628: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.628: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.628: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.628: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.628: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.628: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.629: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.629: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.629: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.629: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.629: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.629: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.630: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.630: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.630: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.630: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.630: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.630: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.630: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.631: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.631: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.631: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.631: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.631: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.631: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.631: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.631: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.632: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.632: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.632: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.632: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.632: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.632: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.632: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.633: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.633: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.633: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.633: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.633: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.633: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.634: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.634: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.634: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.634: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.634: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.634: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.634: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.634: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.635: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.635: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.635: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.635: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.635: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.635: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.636: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.636: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.636: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.636: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.636: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.636: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.636: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.636: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.637: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.637: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.637: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.637: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.637: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.637: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.638: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.638: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.638: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.638: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.638: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.638: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.639: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.639: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.639: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.639: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.639: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.639: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.640: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.640: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.640: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.640: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.640: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.640: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.641: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.641: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.641: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.641: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.641: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.641: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.641: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.642: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.642: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.642: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.642: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.642: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.642: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.642: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.642: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.643: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.643: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.643: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.643: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.643: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.643: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.644: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.644: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.644: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.644: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.644: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.644: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.645: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.645: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.645: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.645: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.645: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.645: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.645: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.646: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.646: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.646: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.646: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.646: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.646: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.647: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.647: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.647: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.647: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.647: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.647: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.647: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.647: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.648: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.648: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.648: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.648: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.648: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.648: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.649: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.649: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.649: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.649: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.649: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.649: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.649: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.649: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.650: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.650: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.650: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.650: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.650: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.650: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.650: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.651: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.651: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.651: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.651: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.651: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.651: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.652: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.652: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.652: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.652: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.652: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.652: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.652: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.653: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.653: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.653: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.653: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.653: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.653: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.653: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.653: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.654: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.654: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.654: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.654: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.654: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.654: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.654: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.655: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.655: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.655: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.655: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.655: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.655: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.656: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.656: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.656: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.656: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.656: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.656: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.656: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.656: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.657: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.657: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.657: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.657: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.657: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.657: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.658: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.658: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.658: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.658: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.658: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.658: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.658: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.659: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.659: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.659: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.659: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.659: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.659: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.659: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.659: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.660: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.660: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.660: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.660: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.660: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.660: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.660: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.661: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.661: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.661: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.661: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.661: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.661: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.662: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.662: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.662: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.662: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.662: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.662: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.662: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.663: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.663: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.663: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.663: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.663: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.663: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.663: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.664: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.664: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.664: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.664: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.664: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.664: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.664: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.664: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.665: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.665: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.665: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.665: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.665: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.665: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.665: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.666: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.666: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.666: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.666: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.666: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.666: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.666: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.667: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.667: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.667: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.667: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.667: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.667: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.668: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.668: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.668: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.668: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.668: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.668: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.669: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.669: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.669: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.669: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.669: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.669: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.670: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.670: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.670: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.670: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.670: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.670: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.670: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.670: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.671: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.671: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.671: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.671: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.671: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.671: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.672: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.672: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.672: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.672: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.672: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.672: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.672: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.672: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.673: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.673: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.673: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.673: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.673: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.673: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.674: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.674: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.674: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.674: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.674: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.674: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.675: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.675: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.675: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.675: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.675: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.675: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.675: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.675: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.676: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.676: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.676: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.676: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.676: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.676: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.677: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.677: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.677: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.677: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.677: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.677: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.678: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.678: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.678: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.678: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.678: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.678: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.678: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.678: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.679: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.679: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.679: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.679: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.679: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.679: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.679: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.679: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.680: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.680: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.680: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.680: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.680: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.680: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.680: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.680: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.681: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.681: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.681: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.681: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.681: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.681: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.682: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.682: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.682: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.682: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.682: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.682: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.682: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.682: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.683: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.683: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.683: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.683: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.683: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.683: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.684: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.684: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.684: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.684: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.684: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.684: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.685: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.685: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.685: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.685: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.685: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.685: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.685: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.685: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.686: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.686: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.686: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.686: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.686: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.686: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.687: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.687: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.687: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.687: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.687: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.687: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.687: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.688: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.688: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.688: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.688: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.688: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.688: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.689: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.689: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.689: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.689: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.689: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.689: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.689: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.690: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.690: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.690: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.690: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.690: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.690: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.690: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.691: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.691: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.691: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.691: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.691: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.691: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.691: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.692: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.692: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.692: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.692: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.692: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.692: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.692: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.693: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.693: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.693: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.693: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.693: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.693: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.694: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.694: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.694: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.694: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.694: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.694: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.694: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.695: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.695: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.695: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.695: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.695: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.695: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.695: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.696: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.696: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.696: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.696: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.696: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.696: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.696: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.696: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.697: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.697: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.697: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.697: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.697: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.697: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.698: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.698: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.698: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.698: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.698: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.698: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.698: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.699: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.699: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.699: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.699: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.699: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.699: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.699: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.700: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.700: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.700: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.700: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.700: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.700: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.700: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.701: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.701: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.701: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.701: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.701: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.701: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.701: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.701: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.702: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.702: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.702: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.702: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.702: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.702: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.702: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.703: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.703: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.703: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.703: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.703: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.703: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.704: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.704: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.704: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.704: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.704: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.704: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.704: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.704: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.705: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.705: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.705: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.705: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.705: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.705: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.705: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.706: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.706: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.706: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.706: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.706: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.706: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.706: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.707: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.707: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.707: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.707: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.707: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.707: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.708: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.708: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.708: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.708: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.708: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.708: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.708: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.708: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.709: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.709: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.709: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.709: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.709: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.709: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.710: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.710: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.710: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.710: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.710: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.710: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.710: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.710: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.711: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.711: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.711: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.711: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.711: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.711: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.711: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.712: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.712: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.712: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.712: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.712: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.712: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.713: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.713: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.713: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.713: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.713: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.713: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.713: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.714: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.714: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.714: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.714: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.714: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.714: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.715: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.715: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.715: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.715: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.715: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.715: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.715: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.715: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.716: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.716: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.716: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.716: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.716: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.716: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.717: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.717: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.717: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.717: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.717: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.717: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.717: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.717: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.718: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.718: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.718: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.718: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.718: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.718: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.719: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.719: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.719: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.719: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.719: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.719: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.719: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.719: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.720: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.720: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.720: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.720: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.720: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.720: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.720: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.721: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.721: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.721: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.721: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.721: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.721: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.722: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.722: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.722: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.722: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.722: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.722: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.722: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.723: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.723: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.723: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.723: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.723: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.723: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.723: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.724: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.724: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.724: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.724: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.724: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.724: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.724: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.724: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.725: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.725: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.725: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.725: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.725: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.725: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.725: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.725: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.725: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.725: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.726: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.726: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.726: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.726: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.726: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.726: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.726: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.727: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.727: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.727: variance_after = 1737 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.727: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.727: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.727: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.727: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.727: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.727: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.727: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.727: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.728: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.728: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.728: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.728: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.728: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.728: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.728: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.728: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.729: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.729: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.729: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.729: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.729: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.729: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.729: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.730: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.730: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.730: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.730: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.730: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.730: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.730: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.731: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.731: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.731: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.731: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.731: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.731: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.732: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.732: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.732: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.732: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.732: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.732: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.732: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.733: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.733: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.733: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.733: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.733: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.733: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.733: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.733: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.734: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.734: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.734: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.734: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.734: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.734: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.735: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.735: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.735: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.735: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.735: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.735: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.735: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.736: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.736: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.736: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.736: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.736: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.736: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.736: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.736: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.737: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.737: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.737: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.737: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.737: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.737: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.738: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.738: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.738: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.738: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.738: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.738: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.738: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.738: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.739: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.739: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.739: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.739: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.739: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.739: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.740: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.740: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.740: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.740: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.740: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.740: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.740: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.741: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.741: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.741: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.741: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.741: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.741: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.742: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.742: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.742: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.742: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.742: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.742: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.742: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.742: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.743: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.743: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.743: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.743: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.743: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.743: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.743: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.744: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.744: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.744: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.744: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.744: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.744: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.745: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.745: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.745: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.745: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.745: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.745: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.745: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.745: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.746: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.746: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.746: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.746: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.746: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.746: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.747: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.747: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.747: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.747: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.747: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.747: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.747: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.747: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.748: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.748: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.748: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.748: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.748: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.748: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.749: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.749: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.749: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.749: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.749: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.749: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.750: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.750: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.750: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.750: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.750: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.750: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.750: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.750: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.751: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.751: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.751: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.751: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.751: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.751: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.752: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.752: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.752: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.752: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.752: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.752: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.753: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.753: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.753: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.753: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.753: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.753: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.753: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.754: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.754: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.754: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.754: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.754: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.754: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.754: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.754: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.755: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.755: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.755: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.755: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.755: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.755: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.755: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.756: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.756: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.756: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.756: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.756: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.756: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.757: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.757: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.757: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.757: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.757: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.757: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.758: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.758: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.758: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.758: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.758: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.758: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.759: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.759: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.759: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.759: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.759: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.759: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.759: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.760: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.760: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.760: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.760: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.760: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.760: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.760: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.760: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.761: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.761: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.761: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.761: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.761: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.761: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.762: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.762: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.762: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.762: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.762: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.762: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.763: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.763: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.763: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.763: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.763: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.763: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.763: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.763: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.764: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.764: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.764: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.764: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.764: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.764: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.764: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.765: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.765: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.765: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.765: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.765: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.766: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.766: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.766: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.766: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.766: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.766: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.767: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.767: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.767: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.767: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.767: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.767: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.767: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.767: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.768: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.768: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.768: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.768: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.768: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.768: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.769: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.769: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.769: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.769: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.769: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.769: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.770: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.770: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.770: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.770: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.770: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.770: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.771: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.771: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.771: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.771: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.771: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.771: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.771: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.771: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.772: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.772: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.772: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.772: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.772: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.773: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.773: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.773: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.773: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.773: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.773: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.773: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.774: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.774: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.774: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.774: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.774: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.774: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.774: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.774: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.775: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.775: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.775: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.775: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.775: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.775: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.776: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.776: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.776: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.776: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.776: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.776: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.777: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.777: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.777: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.777: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.777: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.777: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.778: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.778: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.778: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.778: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.778: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.778: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.779: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.779: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.779: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.779: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.779: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.779: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.779: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.779: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.780: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.780: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.780: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.780: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.780: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.780: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.781: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.781: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.781: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.781: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.781: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.781: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.782: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.782: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.782: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.782: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.782: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.782: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.783: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.783: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.783: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.783: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.783: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.783: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.784: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.784: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.784: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.784: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.784: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.784: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.784: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.784: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.785: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.785: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.785: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.785: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.785: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.785: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.786: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.786: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.786: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.786: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.786: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.786: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.787: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.787: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.787: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.787: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.787: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.787: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.787: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.787: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.788: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.788: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.788: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.788: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.788: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.788: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.789: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.789: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.789: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.789: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.789: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.789: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.790: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.790: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.790: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.790: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.790: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.790: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.791: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.791: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.791: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.791: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.791: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.791: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.792: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.792: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.792: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.792: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.792: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.792: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.792: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.792: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.793: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.793: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.793: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.793: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.793: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.793: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.794: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.794: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.794: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.794: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.794: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.794: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.794: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.794: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.795: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.795: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.795: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.795: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.795: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.795: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.796: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.796: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.796: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.796: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.796: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.796: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.796: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.797: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.797: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.797: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.797: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.797: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.797: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.798: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.798: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.798: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.798: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.798: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.798: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.798: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.798: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.799: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.799: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.799: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.799: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.799: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.799: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.800: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.800: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.800: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.800: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.800: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.800: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.801: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.801: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.801: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.801: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.801: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.801: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.801: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.801: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.802: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.802: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.802: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.802: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.802: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.802: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.803: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.803: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.803: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.803: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.803: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.803: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.804: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.804: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.804: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.804: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.804: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.804: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.804: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.804: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.805: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.805: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.805: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.805: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.805: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.805: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.806: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.806: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.806: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.806: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.806: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.806: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.806: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.807: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.807: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.807: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.807: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.807: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.807: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.808: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.808: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.808: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.808: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.808: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.808: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.808: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.808: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.809: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.809: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.809: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.809: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.809: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.809: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.810: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.810: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.810: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.810: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.810: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.810: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.810: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.810: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.811: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.811: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.811: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.811: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.811: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.811: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.812: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.812: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.812: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.812: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.812: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.812: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.813: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.813: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.813: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.813: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.813: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.813: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.813: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.813: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.813: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.814: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.814: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.814: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.814: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.814: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.814: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.815: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.815: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.815: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.815: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.815: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.815: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.815: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.816: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.816: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.816: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.816: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.816: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.816: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.817: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.817: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.817: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.817: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.817: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.817: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.817: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.817: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.818: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.818: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.818: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.818: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.818: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.818: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.819: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.819: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.819: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.819: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.819: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.819: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.819: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.820: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.820: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.820: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.820: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.820: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.820: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.820: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.821: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.821: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.821: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.821: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.821: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.821: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.821: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.822: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.822: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.822: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.822: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.822: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.822: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.822: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.823: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.823: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.823: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.823: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.823: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.823: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.823: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.823: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.824: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.824: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.824: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.824: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.824: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.825: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.825: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.825: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.825: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.825: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.825: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.825: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.825: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.826: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.826: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.826: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.826: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.826: variance_after = 1526 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.826: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.826: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.826: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.826: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.826: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.827: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.827: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.827: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.827: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.827: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.828: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.828: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.828: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.828: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.828: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.828: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.828: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.828: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.829: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.829: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.829: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.829: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.829: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.829: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.830: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.830: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.830: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.830: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.830: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.830: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.830: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.831: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.831: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.831: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.831: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.831: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.831: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.831: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.832: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.832: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.832: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.832: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.832: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.832: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.832: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.832: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.833: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.833: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.833: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.833: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.833: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.833: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.833: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.834: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.834: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.834: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.834: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.834: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.834: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.834: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.835: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.835: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.835: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.835: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.835: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.835: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.835: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.836: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.836: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.836: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.836: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.836: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.836: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.836: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.837: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.837: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.837: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.837: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.837: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.837: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.838: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.838: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.838: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.838: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.838: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.838: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.838: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.838: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.839: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.839: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.839: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.839: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.839: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.839: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.839: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.840: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.840: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.840: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.840: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.840: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.840: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.841: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.841: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.841: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.841: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.841: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.841: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.841: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.842: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.842: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.842: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.842: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.842: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.842: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.842: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.843: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.843: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.843: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.843: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.843: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.843: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.843: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.844: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.844: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.844: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.844: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.844: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.844: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.844: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.844: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.845: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.845: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.845: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.845: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.845: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.845: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.845: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.846: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.846: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.846: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.846: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.846: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.846: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.846: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.847: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.847: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.847: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.847: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.847: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.847: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.848: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.848: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.848: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.848: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.848: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.848: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.849: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.849: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.849: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.849: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.849: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.849: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.849: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.849: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.850: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.850: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.850: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.850: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.850: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.850: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.851: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.851: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.851: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.851: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.851: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.851: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.852: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.852: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.852: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.852: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.852: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.852: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.853: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.853: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.853: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.853: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.853: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.853: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.853: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.853: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.854: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.854: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.854: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.854: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.854: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.854: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.855: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.855: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.855: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.855: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.855: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.855: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.856: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.856: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.856: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.856: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.856: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.856: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.856: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.856: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.857: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.857: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.857: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.857: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.857: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.857: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.858: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.858: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.858: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.858: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.858: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.858: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.859: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.859: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.859: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.859: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.859: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.859: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.860: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.860: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.860: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.860: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.860: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.860: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.860: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.860: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.861: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.861: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.861: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.861: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.861: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.861: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.862: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.862: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.862: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.862: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.862: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.862: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.863: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.863: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.863: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.863: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.863: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.863: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.863: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.863: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.864: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.864: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.864: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.864: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.864: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.864: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.865: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.865: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.865: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.865: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.865: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.865: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.866: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.866: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.866: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.866: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.866: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.866: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.866: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.866: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.867: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.867: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.867: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.867: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.867: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.867: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.868: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.868: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.868: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.868: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.868: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.868: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.869: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.869: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.869: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.869: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.869: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.869: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.870: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.870: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.870: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.870: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.870: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.870: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.870: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.870: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.871: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.871: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.871: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.871: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.871: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.871: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.872: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.872: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.872: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.872: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.872: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.872: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.873: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.873: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.873: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.873: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.873: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.873: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.874: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.874: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.874: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.874: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.874: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.874: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.874: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.874: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.875: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.875: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.875: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.875: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.875: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.875: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.876: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.876: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.876: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.876: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.876: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.876: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.877: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.877: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.877: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.877: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.877: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.877: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.877: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.877: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.878: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.878: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.878: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.878: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.878: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.878: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.879: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.879: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.879: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.879: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.879: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.879: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.880: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.880: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.880: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.880: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.880: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.880: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.880: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.880: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.881: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.881: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.881: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.881: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.881: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.881: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.882: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.882: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.882: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.882: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.882: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.882: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.883: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.883: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.883: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.883: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.883: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.883: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.883: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.883: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.884: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.884: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.884: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.884: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.884: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.884: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.885: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.885: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.885: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.885: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.885: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.885: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.886: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.886: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.886: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.886: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.886: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.886: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.887: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.887: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.887: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.887: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.887: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.887: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.887: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.887: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.888: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.888: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.888: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.888: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.888: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.888: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.889: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.889: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.889: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.889: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.889: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.889: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.890: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.890: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.890: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.890: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.890: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.890: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.890: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.890: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.891: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.891: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.891: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.891: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.891: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.891: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.892: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.892: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.892: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.892: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.892: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.892: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.893: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.893: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.893: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.893: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.893: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.893: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.893: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.893: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.894: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.894: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.894: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.894: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.894: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.894: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.895: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.895: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.895: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.895: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.895: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.895: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.896: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.896: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.896: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.896: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.896: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.896: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.896: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.896: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.897: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.897: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.897: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.897: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.897: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.897: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.898: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.898: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.898: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.898: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.898: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.898: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.899: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.899: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.899: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.899: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.899: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.899: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.900: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.900: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.900: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.900: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.900: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.900: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.900: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.900: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.901: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.901: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.901: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.901: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.901: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.901: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.902: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.902: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.902: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.902: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.902: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.902: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.903: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.903: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.903: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.903: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.903: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.903: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.903: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.903: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.904: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.904: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.904: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.904: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.904: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.904: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.905: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.905: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.905: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.905: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.905: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.905: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.906: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.906: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.906: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.906: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.906: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.906: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.906: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.907: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.907: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.907: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.907: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.907: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.907: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.907: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.908: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.908: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.908: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.908: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.908: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.908: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.909: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.909: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.909: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.909: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.909: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.909: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.910: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.910: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.910: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.910: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.910: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.910: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.910: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.910: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.911: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.911: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.911: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.911: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.911: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.911: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.912: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.912: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.912: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.912: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.912: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.912: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.913: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.913: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.913: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.913: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.913: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.913: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.913: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.913: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.914: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.914: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.914: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.914: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.914: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.914: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.915: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.915: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.915: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.915: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.915: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.915: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.916: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.916: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.916: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.916: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.916: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.916: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.917: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.917: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.917: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.917: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.917: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.917: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.917: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.917: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.918: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.918: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.918: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.918: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.918: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.918: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.919: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.919: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.919: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.919: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.919: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.919: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.920: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.920: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.920: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.920: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.920: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.920: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.920: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.920: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.921: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.921: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.921: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.921: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.921: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.921: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.922: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.922: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.922: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.922: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.922: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.922: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.923: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.923: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.923: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.923: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.923: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.923: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.923: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.923: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.924: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.924: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.924: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.924: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.924: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.924: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.925: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.925: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.925: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.925: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.925: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.925: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.926: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.926: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.926: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.926: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.926: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.926: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.927: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.927: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.927: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.927: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.927: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.927: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.927: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.927: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.928: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.928: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.928: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.928: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.928: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.928: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.929: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.929: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.929: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.929: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.929: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.929: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.930: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.930: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.930: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.930: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.930: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.930: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.930: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.930: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.931: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.931: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.931: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.931: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.931: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.931: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.932: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.932: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.932: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.932: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.932: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.932: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.932: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.932: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.932: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.932: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.933: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.933: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.933: [vfs7552] CAPTURE_NUM_STATES entering state 2 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.933: [vfs7552] REQUEST CHUNK entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.933: Sending vfs7552_read_image_chunk 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.934: [vfs7552] REQUEST CHUNK completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.934: [vfs7552] CAPTURE_NUM_STATES entering state 3 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.934: [vfs7552] CAPTURE_NUM_STATES entering state 4 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.934: Cleaning image 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.934: variance_after = 1435 186s 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.934: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.934: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.934: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.934: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.935: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.935: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.935: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.935: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.935: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.935: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.935: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.936: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.936: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.936: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.936: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.936: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.937: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.937: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.937: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.937: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.937: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.937: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.937: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.937: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.938: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.938: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.938: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.938: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.938: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.938: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.938: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.939: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.939: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.939: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.939: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.939: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.940: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.940: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.940: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.940: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.940: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.940: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.940: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.940: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.941: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.941: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.941: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.941: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.941: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.941: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.942: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.942: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.942: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.942: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.942: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.942: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.943: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.943: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.943: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.943: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.943: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.943: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.944: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.944: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.944: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.944: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.944: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.944: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.945: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.945: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.945: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.945: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.945: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.945: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.945: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.945: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.946: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.946: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.946: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.946: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.946: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.946: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.947: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.947: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.947: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.947: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.947: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.947: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.948: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.948: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.948: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.948: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.948: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.948: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.949: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.949: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.949: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.949: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.949: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.949: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.950: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.950: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.950: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.950: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.950: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.950: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.950: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.950: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.951: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.951: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.951: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.951: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.951: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.951: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.952: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.952: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.952: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.952: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.952: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.952: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.953: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.953: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.953: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.953: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.953: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.953: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.954: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.954: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.954: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.954: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.954: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.954: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.955: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.955: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.955: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.955: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.955: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.955: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.955: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.955: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.956: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.956: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.956: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.956: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.956: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.957: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.957: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.957: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.957: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.957: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.957: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.957: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.958: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.958: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.958: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.958: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.958: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.958: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.958: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.958: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.959: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.959: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.959: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.959: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.959: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.959: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.960: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.960: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.960: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.960: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.960: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.960: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.961: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.961: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.961: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.961: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.961: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.961: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.962: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.962: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.962: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.962: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.962: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.962: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.962: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.962: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.963: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.963: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.963: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.963: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.963: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.963: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.964: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.964: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.964: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.964: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.964: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.964: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.965: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.965: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.965: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.965: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.965: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.965: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.966: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.966: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.966: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.966: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.966: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.966: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.966: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.966: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.967: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.967: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.967: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.967: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.967: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.967: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.968: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.968: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.968: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.968: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.968: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.968: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.969: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.969: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.969: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.969: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.969: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.969: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.969: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.969: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.970: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.970: Sending vfs7552_is_image_ready 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] QUERY DATA READY entering state 1 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.970: Receiving 64 bytes 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.970: Got 6 bytes out of 64 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] QUERY DATA READY completed successfully 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 186s (process:2469): libfprint-SSM-DEBUG: 00:01:18.970: [vfs7552] QUERY DATA READY entering state 0 186s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.970: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.971: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.971: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.971: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.971: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.971: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.971: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.972: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.972: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.972: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.972: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.972: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.972: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.972: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.972: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.973: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.973: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.973: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.973: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.973: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.973: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.974: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.974: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.974: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.974: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.974: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.974: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.975: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.975: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.975: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.975: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.975: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.975: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.975: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.975: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.976: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.976: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.976: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.976: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.976: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.976: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.977: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.977: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.977: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.977: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.977: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.977: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.978: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.978: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.978: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.978: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.978: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.978: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.979: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.979: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.979: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.979: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.979: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.979: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.979: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.979: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.980: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.980: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.980: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.980: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.980: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.980: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.981: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.981: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.981: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.981: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.981: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.981: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.982: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.982: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.982: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.982: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.982: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.982: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.982: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.982: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.983: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.983: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.983: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.983: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.983: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.983: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.984: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.984: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.984: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.984: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.984: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.984: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.985: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.985: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.985: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.985: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.985: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.985: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.986: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.986: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.986: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.986: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.986: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.986: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.986: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.986: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.987: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.987: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.987: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.987: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.987: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.987: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.988: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.988: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.988: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.988: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.988: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.988: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.988: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.989: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.989: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.989: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.989: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.989: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.990: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.990: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.990: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.990: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.990: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.990: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.990: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.990: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.991: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.991: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.991: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.991: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.991: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.991: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.992: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.992: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.992: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.992: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.992: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.992: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.993: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.993: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.993: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.993: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.993: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.993: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.994: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.994: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.994: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.994: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.994: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.994: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.994: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.995: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.995: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.995: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.995: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.995: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.995: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.995: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.996: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.996: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.996: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.996: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.996: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.996: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.997: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.997: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.997: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.997: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.997: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.997: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.998: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.998: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.998: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.998: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.998: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.998: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.998: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.998: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.999: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.999: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.999: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.999: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:18.999: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:18.999: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.000: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.000: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.000: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.000: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.000: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.000: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.001: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.001: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.001: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.001: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.001: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.001: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.001: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.001: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.002: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.002: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.002: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.002: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.002: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.002: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.003: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.003: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.003: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.003: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.003: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.003: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.004: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.004: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.004: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.004: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.004: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.004: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.005: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.005: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.005: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.005: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.005: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.005: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.005: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.005: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.006: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.006: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.006: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.006: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.006: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.006: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.007: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.007: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.007: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.007: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.007: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.007: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.008: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.008: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.008: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.008: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.008: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.008: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.009: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.009: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.009: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.009: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.009: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.009: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.009: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.009: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.010: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.010: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.010: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.010: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.010: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.010: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.011: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.011: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.011: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.011: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.011: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.011: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.012: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.012: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.012: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.012: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.012: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.012: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.012: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.012: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.013: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.013: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.013: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.013: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.013: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.013: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.014: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.014: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.014: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.014: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.014: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.014: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.015: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.015: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.015: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.015: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.015: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.015: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.016: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.016: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.016: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.016: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.016: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.016: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.016: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.016: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.017: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.017: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.017: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.017: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.017: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.017: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.018: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.018: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.018: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.018: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.018: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.018: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.019: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.019: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.019: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.019: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.019: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.019: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.019: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.019: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.020: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.020: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.020: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.020: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.020: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.020: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.021: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.021: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.021: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.021: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.021: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.021: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.022: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.022: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.022: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.022: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.022: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.022: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.022: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.022: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.023: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.023: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.023: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.023: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.023: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.023: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.024: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.024: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.024: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.024: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.024: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.024: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.025: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.025: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.025: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.025: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.025: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.025: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.026: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.026: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.026: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.026: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.026: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.026: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.026: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.026: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.027: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.027: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.027: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.027: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.027: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.027: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.028: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.028: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.028: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.028: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.028: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.028: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.029: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.029: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.029: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.029: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.029: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.029: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.029: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.029: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.030: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.030: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.030: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.030: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.030: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.030: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.031: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.031: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.031: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.031: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.031: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.031: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.032: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.032: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.032: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.032: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.032: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.032: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.033: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.033: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.033: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.033: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.033: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.033: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.033: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.033: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.034: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.034: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.034: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.034: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.034: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.034: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.035: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.035: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.035: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.035: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.035: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.035: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.036: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.036: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.036: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.036: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.036: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.036: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.036: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.036: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.037: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.037: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.037: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.037: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.037: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.037: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.038: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.038: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.038: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.038: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.038: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.038: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.039: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.039: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.039: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.039: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.039: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.039: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.039: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.039: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.040: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.040: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.040: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.040: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.040: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.040: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.041: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.041: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.041: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.041: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.041: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.041: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.042: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.042: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.042: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.042: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.042: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.042: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.043: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.043: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.043: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.043: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.043: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.043: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.043: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.043: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.044: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.044: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.044: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.044: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.044: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.044: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.045: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.045: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.045: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.045: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.045: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.045: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.046: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.046: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.046: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.046: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.046: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.046: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.046: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.046: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.047: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.047: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.047: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.047: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.047: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.047: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.047: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.048: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.048: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.048: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.048: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.048: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.048: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.048: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.048: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.049: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.049: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.049: [vfs7552] CAPTURE_NUM_STATES entering state 4 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.049: Cleaning image 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.049: variance_after = 1425 187s 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.049: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.049: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.050: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.050: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.050: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.050: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.050: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.050: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.050: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.050: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.051: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.051: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.051: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.051: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.051: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.051: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.052: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.052: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.052: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.052: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.052: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.052: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.053: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.053: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.053: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.053: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.053: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.053: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.054: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.054: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.054: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.054: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.054: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.054: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.054: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.054: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.055: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.055: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.055: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.055: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.055: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.055: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.056: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.056: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.056: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.056: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.056: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.056: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.057: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.057: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.057: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.057: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.057: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.057: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.057: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.057: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.058: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.058: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.058: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.058: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.058: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.058: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.059: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.059: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.059: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.059: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.059: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.059: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.060: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.060: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.060: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.060: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.060: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.060: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.061: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.061: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.061: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.061: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.061: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.061: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.061: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.061: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.062: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.062: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.062: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.062: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.062: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.062: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.063: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.063: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.063: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.063: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.063: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.063: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.064: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.064: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.064: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.064: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.064: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.064: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.064: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.064: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.065: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.065: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.065: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.065: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.065: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.065: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.066: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.066: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.066: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.066: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.066: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.066: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.067: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.067: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.067: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.067: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.067: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.067: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.068: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.068: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.068: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.068: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.068: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.068: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.069: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.069: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.069: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.069: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.069: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.069: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.069: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.069: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.070: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.070: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.070: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.070: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.070: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.070: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.070: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.070: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.071: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.071: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.071: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.071: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.071: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.071: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.071: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.071: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.072: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.072: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.072: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.072: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.072: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.072: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.072: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.072: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.073: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.073: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.073: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.073: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.073: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.073: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.074: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.074: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.074: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.074: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.074: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.074: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.075: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.075: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.075: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.075: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.075: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.075: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.076: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.076: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.076: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.076: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.076: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.076: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.076: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.076: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.077: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.077: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.077: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.077: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.077: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.077: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.078: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.078: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.078: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.078: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.078: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.078: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.079: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.079: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.079: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.079: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.079: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.079: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.080: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.080: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.080: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.080: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.080: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.080: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.080: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.080: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.081: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.081: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.081: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.081: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.081: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.081: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.082: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.082: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.082: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.082: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.082: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.082: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.083: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.083: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.083: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.083: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.083: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.083: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.083: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.083: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.084: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.084: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.084: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.084: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.084: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.084: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.085: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.085: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.085: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.085: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.085: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.085: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.086: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.086: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.086: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.086: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.086: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.086: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.087: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.087: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.087: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.087: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.087: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.087: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.087: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.087: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.088: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.088: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.088: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.088: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.088: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.088: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.089: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.089: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.089: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.089: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.089: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.089: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.090: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.090: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.090: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.090: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.090: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.090: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.091: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.091: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.091: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.091: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.091: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.091: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.092: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.092: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.092: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.092: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.092: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.092: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.093: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.093: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.093: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.093: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.093: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.093: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.093: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.093: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.094: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.094: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.094: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.094: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.094: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.094: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.094: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.094: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.095: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.095: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.095: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.095: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.095: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.095: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.096: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.096: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.096: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.096: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.096: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.096: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.097: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.097: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.097: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.097: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.097: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.097: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.098: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.098: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.098: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.098: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.098: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.098: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.099: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.099: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.099: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.099: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.099: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.099: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.100: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.100: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.100: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.100: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.100: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.100: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.101: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.101: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.101: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.101: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.101: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.101: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.102: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.102: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.102: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.102: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.102: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.102: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.102: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.103: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.103: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.103: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.103: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.103: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.103: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.103: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.104: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.104: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.104: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.104: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.104: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.104: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.105: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.105: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.105: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.105: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.105: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.106: [vfs7552] CAPTURE_NUM_STATES entering state 4 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.106: Cleaning image 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.106: variance_after = 1532 187s 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.106: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.106: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.106: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.106: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.107: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.107: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.107: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.107: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.107: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.107: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.108: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.108: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.108: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.108: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.108: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.108: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.108: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.108: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.109: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.109: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.109: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.109: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.109: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.109: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.110: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.110: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.110: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.110: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.110: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.110: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.110: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.111: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.111: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.111: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.111: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.111: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.112: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.112: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.112: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.112: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.112: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.112: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.112: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.112: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.113: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.113: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.113: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.113: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.113: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.113: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.114: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.114: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.114: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.114: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.114: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.114: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.114: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.115: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.115: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.115: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.115: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.115: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.115: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.115: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.116: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.116: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.116: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.116: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.116: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.116: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.117: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.117: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.117: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.117: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.117: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.117: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.118: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.118: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.118: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.118: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.118: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.118: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.118: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.118: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.119: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.119: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.119: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.119: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.119: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.119: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.119: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.119: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.120: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.120: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.120: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.120: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.120: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.120: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.121: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.121: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.121: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.121: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.121: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.121: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.122: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.122: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.122: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.122: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.122: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.122: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.122: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.122: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.123: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.123: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.123: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.123: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.123: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.123: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.123: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.123: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.124: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.124: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.124: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.124: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.124: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.124: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.124: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.124: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.125: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.125: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.125: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.125: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.125: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.125: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.125: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.125: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.126: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.126: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.126: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.126: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.126: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.126: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.126: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.126: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.127: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.127: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.127: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.127: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.127: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.127: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.127: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.127: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.128: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.128: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.128: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.128: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.128: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.128: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.129: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.129: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.129: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.129: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.129: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.129: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.130: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.130: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.130: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.130: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.130: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.130: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.130: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.130: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.131: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.131: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.131: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.131: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.131: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.131: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.131: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.131: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.132: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.132: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.132: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.132: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.132: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.132: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.132: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.132: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.133: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.133: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.133: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.133: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.133: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.133: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.133: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.133: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.134: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.134: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.134: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.134: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.134: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.134: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.135: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.135: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.135: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.135: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.135: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.136: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.136: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.136: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.136: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.136: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.136: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.136: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 4 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.137: Cleaning image 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.137: variance_after = 1691 187s 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.137: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.137: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.137: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.137: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.137: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.138: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.138: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.138: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.138: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.138: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.139: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.139: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.139: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.139: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.139: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.139: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.139: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.139: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.140: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.140: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.140: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.140: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.140: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.140: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.141: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.141: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.141: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.141: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.141: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.141: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.142: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.142: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.142: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.142: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.142: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.142: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.142: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.142: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.143: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.143: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.143: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.143: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.143: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.143: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.144: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.144: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.144: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.144: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.144: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.144: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.145: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.145: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.145: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.145: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.145: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.145: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.145: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.145: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.146: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.146: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.146: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.146: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.146: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.146: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.147: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.147: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.147: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.147: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.147: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.147: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.148: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.148: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.148: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.148: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.148: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.148: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.148: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.148: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.149: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.149: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.149: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.149: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.149: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.149: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.150: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.150: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.150: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.150: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.150: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.150: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.151: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.151: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.151: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.151: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.151: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.151: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.151: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.151: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.152: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.152: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.152: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.152: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.152: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.152: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.153: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.153: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.153: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.153: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.153: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.153: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.154: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.154: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.154: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.154: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.154: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.154: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.155: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.155: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.155: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.155: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.155: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.155: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.155: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.155: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.156: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.156: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.156: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.156: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.156: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.156: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.156: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.157: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.157: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.157: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.157: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.157: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.158: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.158: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.158: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.158: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.158: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.158: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.159: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.159: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.159: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.159: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.159: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.159: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.159: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.159: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.160: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.160: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.160: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.160: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.160: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.160: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.160: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.160: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.161: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.161: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.161: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.161: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.161: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.161: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.161: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.161: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.162: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.162: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.162: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.162: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.162: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.162: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.162: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.162: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.163: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.163: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.163: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.163: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.163: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.163: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.164: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.164: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.164: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.164: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.164: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.164: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.165: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.165: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.165: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.165: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.165: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.165: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.165: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.165: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.166: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.166: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.166: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.166: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.166: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.166: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.166: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.167: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.167: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.167: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.167: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.167: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.168: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.168: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.168: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.168: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.169: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.169: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.169: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 4 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.169: Cleaning image 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.169: variance_after = 1845 187s 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.169: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.169: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.170: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.170: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.170: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.170: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.170: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.170: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.171: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.171: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.171: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.171: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.171: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.171: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.171: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.171: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.172: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.172: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.172: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.172: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.172: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.172: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.173: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.173: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.173: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.173: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.173: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.173: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.173: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.173: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.174: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.174: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.174: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.174: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.174: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.174: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.174: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.174: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.175: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.175: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.175: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.175: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.175: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.175: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.175: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.175: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.176: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.176: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.176: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.176: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.176: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.176: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.177: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.177: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.177: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.177: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.177: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.177: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.178: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.178: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.178: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.178: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.178: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.178: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.179: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.179: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.179: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.179: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.179: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.179: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.179: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.179: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.180: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.180: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.180: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.180: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.180: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.180: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.180: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.180: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.181: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.181: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.181: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.181: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.181: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.181: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.181: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.181: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.182: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.182: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.182: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.182: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.182: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.182: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.182: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.182: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.183: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.183: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.183: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.183: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.183: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.183: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.184: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.184: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.184: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.184: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.184: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.184: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.185: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.185: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.185: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.185: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.185: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.185: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.186: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.186: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.186: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.186: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.186: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.186: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.186: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.186: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.187: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.187: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.187: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.187: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.187: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.187: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.188: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.188: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.188: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.188: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.188: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.188: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.189: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.189: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.189: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.189: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.189: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.189: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.190: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.190: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.190: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.190: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.190: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.190: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.190: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.190: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.191: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.191: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.191: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.191: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.191: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.191: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.191: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.192: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.192: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.192: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.192: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.192: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.193: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.193: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.193: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.193: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.193: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.193: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.193: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.193: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.194: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.194: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.194: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.194: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.194: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.194: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.195: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.195: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.195: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.195: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.195: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.195: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.196: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.196: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.196: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.196: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.196: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.196: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.196: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.196: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.197: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.197: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.197: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.197: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.197: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.197: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.198: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.198: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.198: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.198: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.198: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.198: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.198: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.199: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.199: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.199: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.199: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.199: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.200: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.200: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.200: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.200: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.200: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.200: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.200: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.200: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.201: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.201: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.201: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.201: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.201: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.201: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.201: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.202: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.202: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.202: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.202: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.202: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.203: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.203: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.203: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.203: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.203: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.203: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.203: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.203: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.204: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.204: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.204: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.204: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.204: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.204: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.204: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.205: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.205: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.205: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.205: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.205: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.205: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.206: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.206: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.206: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.206: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.207: [vfs7552] CAPTURE_NUM_STATES entering state 4 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.207: Cleaning image 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.207: variance_after = 2342 187s 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.207: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.207: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.207: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.207: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.208: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.208: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.208: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.208: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.208: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.208: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.209: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.209: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.209: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.209: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.209: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.209: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.209: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.209: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.210: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.210: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.210: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.210: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.210: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.210: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.211: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.211: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.211: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.211: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.211: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.211: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.211: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.211: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.212: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.212: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.212: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.212: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.212: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.212: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.212: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.212: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.213: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.213: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.213: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.213: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.213: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.213: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.213: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.213: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.214: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.214: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.214: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.214: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.214: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.214: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.214: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.215: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.215: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.215: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.215: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.215: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.216: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.216: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.216: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.216: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.216: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.216: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.216: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.216: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.217: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.217: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.217: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.217: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.217: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.217: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.218: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.218: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.218: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.218: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.218: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.218: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.219: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.219: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.219: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.219: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.219: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.219: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.219: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.219: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.220: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.220: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.220: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.220: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.220: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.220: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.221: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.221: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.221: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.221: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.221: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.221: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.222: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.222: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.222: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.222: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.222: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.222: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.222: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.222: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.223: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.223: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.223: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.223: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.223: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.223: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.224: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.224: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.224: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.224: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.224: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.224: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.225: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.225: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.225: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.225: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.225: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.225: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.225: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.225: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.226: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.226: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.226: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.226: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.226: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.226: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.227: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.227: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.227: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.227: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.227: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.227: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.228: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.228: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.228: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.228: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.228: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.228: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.228: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.228: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.229: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.229: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.229: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.229: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.229: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.229: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.230: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.230: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.230: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.230: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.230: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.230: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.231: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.231: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.231: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.231: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.231: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.231: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.231: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.231: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.232: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.232: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.232: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.232: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.232: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.232: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.233: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.233: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.233: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.233: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.233: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.233: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.234: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.234: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.234: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.234: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.234: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.234: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.234: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.234: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.235: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.235: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.235: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.235: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.235: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.235: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.236: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.236: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.236: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.236: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.236: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.236: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.237: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.237: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.237: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.237: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.237: [vfs7552] QUERY DATA READY entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.237: Sending vfs7552_is_image_ready 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.238: [vfs7552] QUERY DATA READY entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.238: Receiving 64 bytes 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.238: Got 6 bytes out of 64 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.238: [vfs7552] QUERY DATA READY completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.238: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.238: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.238: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.239: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.239: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.239: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 2 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.239: [vfs7552] REQUEST CHUNK entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.239: Sending vfs7552_read_image_chunk 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.240: [vfs7552] REQUEST CHUNK completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.240: [vfs7552] CAPTURE_NUM_STATES entering state 3 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.240: [vfs7552] CAPTURE_NUM_STATES entering state 4 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.240: Cleaning image 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.240: variance_after = 16 187s 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.240: [vfs7552] CAPTURE_NUM_STATES completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.240: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.250: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.250: [vfs7552] STOP CAPTURE entering state 0 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.250: Sending vfs7552_cmd_04 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.251: [vfs7552] STOP CAPTURE entering state 1 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.251: Receiving 64 bytes 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.251: [vfs7552] STOP CAPTURE entering state 2 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.251: Sending vfs7552_cmd_52 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.251: [vfs7552] STOP CAPTURE entering state 3 187s (process:2469): libfprint-vfs7552-DEBUG: 00:01:19.251: Receiving 64 bytes 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.252: [vfs7552] STOP CAPTURE completed successfully 187s (process:2469): libfprint-SSM-DEBUG: 00:01:19.252: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 187s (process:2469): libfprint-device-DEBUG: 00:01:19.252: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:2469): libfprint-image_device-DEBUG: 00:01:19.252: Image device reported finger status: off 187s (process:2469): libfprint-image_device-DEBUG: 00:01:19.252: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:2469): libfprint-image_device-DEBUG: 00:01:19.252: Deactivating image device 187s (process:2469): libfprint-image_device-DEBUG: 00:01:19.252: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 187s (process:2469): libfprint-image_device-DEBUG: 00:01:19.252: Image device deactivation completed 187s (process:2469): libfprint-image_device-DEBUG: 00:01:19.252: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 187s (process:2469): libfprint-device-DEBUG: 00:01:19.252: Device reported capture completion 187s (process:2469): libfprint-device-DEBUG: 00:01:19.252: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 187s (process:2469): libfprint-device-DEBUG: 00:01:19.252: Updated temperature model after 1.85 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2469): libfprint-image_device-DEBUG: 00:01:19.252: Image device close completed 187s (process:2469): libfprint-device-DEBUG: 00:01:19.252: Device reported close completion 187s (process:2469): libfprint-device-DEBUG: 00:01:19.252: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:2469): libfprint-device-DEBUG: 00:01:19.252: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s ** (umockdev-run:2465): DEBUG: 00:01:19.323: umockdev.vala:154: Removing test bed /tmp/umockdev.Z4M212 187s (umockdev-run:2465): GLib-DEBUG: 00:01:19.325: unsetenv() is not thread-safe and should not be used after threads are created 187s Comparing PNGs /tmp/libfprint-umockdev-test-fa0pmp4g/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 187s PASS: libfprint-2/driver-vfs7552.test 187s Running test: libfprint-2/driver-aes3500.test 187s ** (umockdev-run:2478): DEBUG: 00:01:19.372: umockdev.vala:127: Created udev test bed /tmp/umockdev.I70512 187s ** (umockdev-run:2478): DEBUG: 00:01:19.373: 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 187s ** (umockdev-run:2478): DEBUG: 00:01:19.375: 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) 187s ** (umockdev-run:2478): DEBUG: 00:01:19.376: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.I70512/dev/bus/usb/003/004 187s ** (umockdev-run:2478): DEBUG: 00:01:19.376: 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 187s ** (umockdev-run:2478): DEBUG: 00:01:19.379: 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) 187s ** (umockdev-run:2478): DEBUG: 00:01:19.380: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.I70512/dev/bus/usb/003/003 187s ** (umockdev-run:2478): DEBUG: 00:01:19.380: 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 187s ** (umockdev-run:2478): DEBUG: 00:01:19.382: 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) 187s ** (umockdev-run:2478): DEBUG: 00:01:19.383: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.I70512/dev/bus/usb/003/002 187s ** (umockdev-run:2478): DEBUG: 00:01:19.383: 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 187s ** (umockdev-run:2478): DEBUG: 00:01:19.385: 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) 187s ** (umockdev-run:2478): DEBUG: 00:01:19.386: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.I70512/dev/bus/usb/003/001 187s ** (umockdev-run:2478): DEBUG: 00:01:19.386: 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 187s ** (umockdev-run:2478): DEBUG: 00:01:19.387: 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) 187s ** (umockdev-run:2478): DEBUG: 00:01:19.388: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 187s ** (umockdev-run:2478): DEBUG: 00:01:19.389: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 187s ** (umockdev-run:2478): DEBUG: 00:01:19.390: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 187s ** (umockdev-run:2478): DEBUG: 00:01:19.391: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 187s ** (umockdev-run:2478): DEBUG: 00:01:19.392: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0 187s ** (umockdev-run:2478): DEBUG: 00:01:19.392: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 187s (umockdev-run:2478): GLib-GIO-DEBUG: 00:01:19.393: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 187s (process:2482): libfprint-context-DEBUG: 00:01:19.450: Initializing FpContext (libfprint version 1.94.8+tod1) 187s (process:2482): libfprint-tod-DEBUG: 00:01:19.450: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 187s (process:2482): libfprint-context-DEBUG: 00:01:19.452: No driver found for USB device 2230:0006 187s (process:2482): libfprint-context-DEBUG: 00:01:19.452: No driver found for USB device 2230:0006 187s (process:2482): libfprint-context-DEBUG: 00:01:19.452: No driver found for USB device 1D6B:0002 187s (process:2482): libfprint-device-DEBUG: 00:01:19.453: Device reported probe completion 187s (process:2482): libfprint-device-DEBUG: 00:01:19.453: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s (process:2482): libfprint-device-DEBUG: 00:01:19.453: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.453: Image device open completed 187s (process:2482): libfprint-device-DEBUG: 00:01:19.454: Device reported open completion 187s (process:2482): libfprint-device-DEBUG: 00:01:19.454: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s (process:2482): libfprint-device-DEBUG: 00:01:19.454: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2482): libfprint-device-DEBUG: 00:01:19.454: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.454: Activating image device 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.454: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 187s (process:2482): libfprint-aeslib-DEBUG: 00:01:19.454: write 50 regs 187s (process:2482): libfprint-aeslib-DEBUG: 00:01:19.456: all registers written 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.456: Image device activation completed 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.456: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.456: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 187s (process:2482): libfprint-aeslib-DEBUG: 00:01:19.456: write 6 regs 187s (process:2482): libfprint-device-DEBUG: 00:01:19.457: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2482): libfprint-aeslib-DEBUG: 00:01:19.457: all registers written 187s (process:2482): libfprint-device-DEBUG: 00:01:19.458: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.458: Image device reported finger status: on 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.458: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 187s (process:2482): libfprint-aes3k-DEBUG: 00:01:19.458: frame header byte e0 187s (process:2482): libfprint-aes3k-DEBUG: 00:01:19.458: frame header byte e1 187s (process:2482): libfprint-aes3k-DEBUG: 00:01:19.458: frame header byte e2 187s (process:2482): libfprint-aes3k-DEBUG: 00:01:19.458: frame header byte e3 187s (process:2482): libfprint-aes3k-DEBUG: 00:01:19.458: frame header byte e4 187s (process:2482): libfprint-aes3k-DEBUG: 00:01:19.458: frame header byte e5 187s (process:2482): libfprint-aes3k-DEBUG: 00:01:19.458: frame header byte e6 187s (process:2482): libfprint-aes3k-DEBUG: 00:01:19.458: frame header byte e7 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.458: Image device captured an image 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 187s (process:2482): libfprint-device-DEBUG: 00:01:19.459: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2482): libfprint-device-DEBUG: 00:01:19.459: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.459: Image device reported finger status: off 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.459: Deactivating image device 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.459: Image device deactivation completed 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 187s (process:2482): libfprint-image-DEBUG: 00:01:19.479: Minutiae scan completed in 0.020637 secs 187s (process:2482): libfprint-device-DEBUG: 00:01:19.479: Device reported capture completion 187s (process:2482): libfprint-device-DEBUG: 00:01:19.479: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 187s (process:2482): libfprint-device-DEBUG: 00:01:19.479: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 187s (process:2482): libfprint-image_device-DEBUG: 00:01:19.480: Image device close completed 187s (process:2482): libfprint-device-DEBUG: 00:01:19.480: Device reported close completion 187s (process:2482): libfprint-device-DEBUG: 00:01:19.480: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:2482): libfprint-device-DEBUG: 00:01:19.480: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s ** (umockdev-run:2478): DEBUG: 00:01:19.575: umockdev.vala:154: Removing test bed /tmp/umockdev.I70512 187s (umockdev-run:2478): GLib-DEBUG: 00:01:19.580: unsetenv() is not thread-safe and should not be used after threads are created 187s Comparing PNGs /tmp/libfprint-umockdev-test-i3njt3th/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 187s PASS: libfprint-2/driver-aes3500.test 187s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 187s TAP version 14 187s # random seed: R02S982b583318495190bb709a3818b88a16 187s 1..14 187s # Start of device tests 187s # Start of async tests 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 1 /device/async/open 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 2 /device/async/close 187s # End of async tests 187s # Start of sync tests 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 3 /device/sync/open 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 4 /device/sync/close 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 5 /device/sync/get_driver 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 6 /device/sync/get_device_id 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 7 /device/sync/get_name 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 8 /device/sync/get_scan_type 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 9 /device/sync/get_nr_enroll_stages 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 10 /device/sync/supports_identify 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 11 /device/sync/supports_capture 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 12 /device/sync/has_storage 187s # Start of open tests 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 13 /device/sync/open/notify 187s # End of open tests 187s # Start of close tests 187s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 187s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 187s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ff8a4029d0, GType is 2929328496752 187s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 187s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 187s # libfprint-context-DEBUG: created 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 187s # 187s # libfprint-device-DEBUG: Device reported probe completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 187s # 187s # libfprint-device-DEBUG: Device reported open completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 187s # 187s # libfprint-device-DEBUG: Device reported close completion 187s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s ok 14 /device/sync/close/notify 187s # End of close tests 187s # End of sync tests 187s # End of device tests 187s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 187s Running test: libfprint-2/driver-egismoc-05a1.test 187s ** (umockdev-run:2523): DEBUG: 00:01:19.642: umockdev.vala:127: Created udev test bed /tmp/umockdev.QW6B22 187s ** (umockdev-run:2523): DEBUG: 00:01:19.642: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 187s ** (umockdev-run:2523): DEBUG: 00:01:19.644: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 187s ** (umockdev-run:2523): DEBUG: 00:01:19.645: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.QW6B22/dev/bus/usb/001/003 187s ** (umockdev-run:2523): DEBUG: 00:01:19.645: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 187s ** (umockdev-run:2523): DEBUG: 00:01:19.646: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 187s ** (umockdev-run:2523): DEBUG: 00:01:19.647: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.QW6B22/dev/bus/usb/001/001 187s ** (umockdev-run:2523): DEBUG: 00:01:19.647: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 187s ** (umockdev-run:2523): DEBUG: 00:01:19.648: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 187s (process:2527): libfprint-context-DEBUG: 00:01:19.706: Initializing FpContext (libfprint version 1.94.8+tod1) 187s (process:2527): libfprint-tod-DEBUG: 00:01:19.706: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.707: 72628537: ../libfprint/drivers/egismoc/egismoc.c:1597 187s (process:2527): libfprint-context-DEBUG: 00:01:19.707: No driver found for USB device 1D6B:0002 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.707: egismoc_probe enter --> 187s (process:2527): libfprint-device-DEBUG: 00:01:19.708: Device reported probe completion 187s (process:2527): libfprint-device-DEBUG: 00:01:19.708: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.708: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.708: Opening device 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.708: [egismoc] DEV_INIT_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.709: [egismoc] DEV_INIT_STATES entering state 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.709: [egismoc] DEV_INIT_STATES entering state 2 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.709: [egismoc] DEV_INIT_STATES entering state 3 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.710: [egismoc] DEV_INIT_STATES entering state 4 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.710: [egismoc] DEV_INIT_STATES entering state 5 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.710: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.710: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.710: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.710: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.710: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.710: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.710: Firmware version callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.710: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.710: Device firmware version is 9050.1.2.13 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.711: [egismoc] DEV_INIT_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.711: Device reported open completion 187s (process:2527): libfprint-device-DEBUG: 00:01:19.711: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.711: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: List 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.711: [egismoc] LIST_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.711: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.711: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.711: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.711: Number of currently enrolled fingerprints on the device is 3 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.711: [egismoc] LIST_STATES entering state 1 187s (process:2527): libfprint-device-DEBUG: 00:01:19.712: Device reported listing completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.712: [egismoc] LIST_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.712: Completing action FPI_DEVICE_ACTION_LIST in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.712: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Clear storage 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.712: [egismoc] DELETE_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.712: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.712: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.712: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Number of currently enrolled fingerprints on the device is 3 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.712: [egismoc] DELETE_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Get delete command 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.712: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.712: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.713: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.713: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.713: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.713: Delete callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.713: Response prefix valid: yes 187s (process:2527): libfprint-device-DEBUG: 00:01:19.713: Device reported deletion completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.713: [egismoc] DELETE_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.713: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.713: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.713: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.713: List 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.713: [egismoc] LIST_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.713: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.713: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.713: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.713: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.714: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.714: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.714: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.714: Number of currently enrolled fingerprints on the device is 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.714: [egismoc] LIST_STATES entering state 1 187s (process:2527): libfprint-device-DEBUG: 00:01:19.714: Device reported listing completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.714: [egismoc] LIST_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.714: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.714: Completing action FPI_DEVICE_ACTION_LIST in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.714: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2527): libfprint-device-DEBUG: 00:01:19.714: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.714: Enroll 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.714: [egismoc] ENROLL_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.714: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.714: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.714: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.715: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.715: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.715: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.715: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.715: Number of currently enrolled fingerprints on the device is 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.715: [egismoc] ENROLL_STATES entering state 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.715: [egismoc] ENROLL_STATES entering state 2 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.715: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.715: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.715: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.715: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.715: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.715: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.715: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.715: [egismoc] ENROLL_STATES entering state 3 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.716: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.716: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.716: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.716: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.716: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.716: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.716: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.716: [egismoc] ENROLL_STATES entering state 4 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.716: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.716: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.716: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.716: [egismoc] ENROLL_STATES entering state 5 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.716: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.716: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.716: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.717: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.717: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.717: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.717: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.717: [egismoc] ENROLL_STATES entering state 6 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.717: Get check command 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.717: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.717: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.717: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.718: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.718: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.718: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.718: Enroll check callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.718: Response suffix valid: yes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.718: [egismoc] ENROLL_STATES entering state 7 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.718: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.718: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.718: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.718: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.718: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.718: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.718: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.719: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.719: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.719: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.719: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.719: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.719: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.719: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.719: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.719: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.719: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.719: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.719: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.719: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.720: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.720: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.720: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.720: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.720: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.720: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.720: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.720: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.721: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.721: Partial capture successful. Please touch the sensor again (1/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.721: Device reported enroll progress, reported 1 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.721: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.721: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.721: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.721: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.721: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.721: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.721: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.721: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.721: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.721: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.721: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.721: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.721: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.722: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.722: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.722: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.722: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.722: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.722: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.722: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Partial capture successful. Please touch the sensor again (2/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.722: Device reported enroll progress, reported 2 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.722: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.722: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.722: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.723: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.723: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.723: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.723: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.723: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.723: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.723: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.723: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.723: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.724: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.724: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.724: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.724: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.724: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.724: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.724: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Response prefix valid: NO 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Response prefix valid: NO 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Response prefix valid: yes 187s (process:2527): libfprint-device-DEBUG: 00:01:19.724: Device reported enroll progress, reported 2 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.724: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.724: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.724: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.725: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.725: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.725: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.725: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.725: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.725: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.725: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.725: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.725: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.725: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.725: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.725: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.725: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.725: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.726: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.726: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.726: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.726: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.726: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Partial capture successful. Please touch the sensor again (3/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.726: Device reported enroll progress, reported 3 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.726: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.726: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.726: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.727: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.727: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.727: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.727: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.727: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.727: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.727: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.727: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.727: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.727: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.727: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.727: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.727: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.727: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.728: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.728: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.728: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.728: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.728: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Partial capture successful. Please touch the sensor again (4/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.728: Device reported enroll progress, reported 4 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.728: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.728: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.728: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.728: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.729: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.729: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.729: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.729: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.729: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.729: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.729: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.729: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.729: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.729: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.729: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.729: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.729: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.730: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.730: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.730: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.730: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.730: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Partial capture successful. Please touch the sensor again (5/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.730: Device reported enroll progress, reported 5 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.730: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.730: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.730: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.730: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.731: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.731: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.731: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.731: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.731: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.731: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.731: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.731: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.731: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.731: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.732: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.732: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Partial capture successful. Please touch the sensor again (6/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.732: Device reported enroll progress, reported 6 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.732: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.732: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.732: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.732: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.732: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.732: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.732: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.733: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.733: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.733: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.733: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.733: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.733: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.733: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.733: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.733: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.733: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.733: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.733: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.733: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.733: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.734: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Partial capture successful. Please touch the sensor again (7/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.734: Device reported enroll progress, reported 7 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.734: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.734: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.734: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.734: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.734: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.734: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.734: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.734: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.735: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.735: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.735: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.735: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.735: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.735: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.735: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.735: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.735: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.735: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.735: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.735: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.735: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.735: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.736: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Partial capture successful. Please touch the sensor again (8/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.736: Device reported enroll progress, reported 8 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.736: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.736: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.736: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.736: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.736: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.736: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.736: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.736: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.737: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.737: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.737: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.737: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.737: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.737: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.737: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.737: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Partial capture successful. Please touch the sensor again (9/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.737: Device reported enroll progress, reported 9 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.737: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.737: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.737: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.738: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.738: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.738: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.738: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.738: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.738: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.738: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.738: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.738: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.738: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.738: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.738: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.738: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.738: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.739: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.739: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.739: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.739: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.739: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Partial capture successful. Please touch the sensor again (10/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.739: Device reported enroll progress, reported 10 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.739: [egismoc] ENROLL_STATES entering state 12 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.739: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.739: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.739: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.740: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.740: [egismoc] ENROLL_STATES entering state 13 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: New fingerprint ID: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.740: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.740: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.740: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.740: [egismoc] ENROLL_STATES entering state 14 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.740: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.740: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.741: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.741: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.741: [egismoc] ENROLL_STATES entering state 15 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: Enrollment was successful! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.741: Device reported enroll completion 187s (process:2527): libfprint-device-DEBUG: 00:01:19.741: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:2527): libfprint-device-DEBUG: 00:01:19.741: Print for finger FP_FINGER_LEFT_INDEX enrolled 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.741: [egismoc] ENROLL_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.741: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.741: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: List 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.741: [egismoc] LIST_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.741: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.741: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.741: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.741: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Device fingerprint 1: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Number of currently enrolled fingerprints on the device is 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] LIST_STATES entering state 1 187s (process:2527): libfprint-device-DEBUG: 00:01:19.742: Device reported listing completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] LIST_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.742: Completing action FPI_DEVICE_ACTION_LIST in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.742: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-device-DEBUG: 00:01:19.742: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Identify or Verify 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] IDENTIFY_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Device fingerprint 1: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Number of currently enrolled fingerprints on the device is 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] IDENTIFY_STATES entering state 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] IDENTIFY_STATES entering state 2 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.742: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.742: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.743: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.743: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.743: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.743: [egismoc] IDENTIFY_STATES entering state 3 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.743: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.743: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.743: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.743: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.743: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.743: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.743: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.743: [egismoc] IDENTIFY_STATES entering state 4 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.743: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.744: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.744: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.744: [egismoc] IDENTIFY_STATES entering state 5 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.744: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.744: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.744: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.744: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.744: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.744: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.744: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.744: [egismoc] IDENTIFY_STATES entering state 6 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.744: Get check command 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.744: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.744: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.744: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.744: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Identify check callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Identify successful for: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Verifying against: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-device-DEBUG: 00:01:19.745: Device reported verify result 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] IDENTIFY_STATES entering state 7 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] IDENTIFY_STATES entering state 8 187s (process:2527): libfprint-device-DEBUG: 00:01:19.745: Device reported verify completion 187s (process:2527): libfprint-device-DEBUG: 00:01:19.745: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] IDENTIFY_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.745: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.745: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-device-DEBUG: 00:01:19.745: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Identify or Verify 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] IDENTIFY_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.745: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.745: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.746: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.746: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.746: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.746: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.746: Device fingerprint 1: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.746: Number of currently enrolled fingerprints on the device is 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.746: [egismoc] IDENTIFY_STATES entering state 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.746: [egismoc] IDENTIFY_STATES entering state 2 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.746: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.746: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.746: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.746: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.747: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.747: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.747: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.747: [egismoc] IDENTIFY_STATES entering state 3 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.747: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.747: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.747: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.747: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.747: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.747: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.747: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.747: [egismoc] IDENTIFY_STATES entering state 4 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.747: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.747: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.748: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.748: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.748: [egismoc] IDENTIFY_STATES entering state 5 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.748: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.748: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.748: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.748: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.748: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.748: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.748: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.748: [egismoc] IDENTIFY_STATES entering state 6 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.748: Get check command 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.748: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.748: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.748: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.748: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.749: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Identify check callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Identify successful for: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-device-DEBUG: 00:01:19.749: Device reported identify result 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.749: [egismoc] IDENTIFY_STATES entering state 7 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.749: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.749: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.749: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.749: [egismoc] IDENTIFY_STATES entering state 8 187s (process:2527): libfprint-device-DEBUG: 00:01:19.749: Device reported identify completion 187s (process:2527): libfprint-device-DEBUG: 00:01:19.749: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.749: [egismoc] IDENTIFY_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.749: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.749: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.749: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-device-DEBUG: 00:01:19.750: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: Enroll 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.750: [egismoc] ENROLL_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.750: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.750: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.750: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: Device fingerprint 1: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: Number of currently enrolled fingerprints on the device is 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.750: [egismoc] ENROLL_STATES entering state 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.750: [egismoc] ENROLL_STATES entering state 2 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.750: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.750: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.750: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.751: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.751: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.751: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.751: [egismoc] ENROLL_STATES entering state 3 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.751: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.751: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.751: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.751: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.751: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.751: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.751: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.751: [egismoc] ENROLL_STATES entering state 4 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.751: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.752: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.752: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.752: [egismoc] ENROLL_STATES entering state 5 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.752: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.752: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.752: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.752: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.752: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.752: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.752: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.752: [egismoc] ENROLL_STATES entering state 6 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.752: Get check command 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.752: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.752: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.752: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.752: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Enroll check callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Response suffix valid: NO 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Device reported enroll completion 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: List 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] LIST_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Device fingerprint 1: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Number of currently enrolled fingerprints on the device is 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] LIST_STATES entering state 1 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Device reported listing completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] LIST_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Completing action FPI_DEVICE_ACTION_LIST in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-device-DEBUG: 00:01:19.753: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Enroll 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] ENROLL_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.753: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.753: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Device fingerprint 1: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Number of currently enrolled fingerprints on the device is 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] ENROLL_STATES entering state 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] ENROLL_STATES entering state 2 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] ENROLL_STATES entering state 3 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.754: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.754: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.755: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.755: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.755: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.755: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.755: [egismoc] ENROLL_STATES entering state 4 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.755: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.755: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.755: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.755: [egismoc] ENROLL_STATES entering state 5 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.755: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.755: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.755: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.756: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.756: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.756: [egismoc] ENROLL_STATES entering state 6 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Get check command 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.756: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.756: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.756: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Enroll check callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Response suffix valid: yes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.756: [egismoc] ENROLL_STATES entering state 7 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.756: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.756: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.757: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.757: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.757: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.757: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.757: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.757: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.757: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.757: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.757: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.758: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.758: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.758: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.758: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.758: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.758: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.758: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.758: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.758: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.758: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.759: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.759: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Partial capture successful. Please touch the sensor again (1/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.759: Device reported enroll progress, reported 1 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.759: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.759: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.759: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.759: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.759: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.759: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.759: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.760: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.760: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.760: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.760: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.760: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.760: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.760: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.760: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.760: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.760: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.760: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.760: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.760: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.761: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Partial capture successful. Please touch the sensor again (2/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.761: Device reported enroll progress, reported 2 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.761: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.761: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.761: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.761: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.761: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.761: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.761: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.762: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.762: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.762: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.762: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.762: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.762: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.762: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.762: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.762: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.762: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.762: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.762: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.762: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.762: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.763: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Response suffix valid: NO 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Response suffix valid: yes 187s (process:2527): libfprint-device-DEBUG: 00:01:19.763: Device reported enroll progress, reported 2 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.763: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.763: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.763: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.763: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.763: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.763: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.763: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.763: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.764: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.764: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.764: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.764: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.764: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.764: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.764: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Response suffix valid: NO 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Response suffix valid: yes 187s (process:2527): libfprint-device-DEBUG: 00:01:19.764: Device reported enroll progress, reported 2 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.764: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.764: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.764: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.765: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.765: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.765: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.765: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.765: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.765: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.765: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.765: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.765: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.766: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.766: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.766: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.766: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.766: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.766: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.766: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Partial capture successful. Please touch the sensor again (3/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.766: Device reported enroll progress, reported 3 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.766: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.766: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.766: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.767: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.767: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.767: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.767: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.767: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.767: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.767: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.767: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.767: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.768: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.768: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.768: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.768: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.768: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.768: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.768: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Response suffix valid: NO 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Response suffix valid: yes 187s (process:2527): libfprint-device-DEBUG: 00:01:19.768: Device reported enroll progress, reported 3 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.768: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.768: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.768: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.769: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.769: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.769: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.769: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.769: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.769: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.769: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.769: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.769: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.770: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.770: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.770: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.770: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.770: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.770: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.770: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.770: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Partial capture successful. Please touch the sensor again (4/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.770: Device reported enroll progress, reported 4 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.770: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.770: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.770: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.771: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.771: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.771: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.771: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.771: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.771: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.771: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.771: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.771: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.772: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.772: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.772: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.772: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.772: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.772: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.772: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.772: Partial capture successful. Please touch the sensor again (5/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.772: Device reported enroll progress, reported 5 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.773: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.773: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.773: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.773: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.773: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.773: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.773: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.773: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.773: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.773: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.773: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.773: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.773: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.774: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.774: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.774: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.774: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.774: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.774: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.774: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.774: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.774: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.774: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.774: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.774: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.774: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.775: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Partial capture successful. Please touch the sensor again (6/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.775: Device reported enroll progress, reported 6 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.775: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.775: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.775: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.775: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.775: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.775: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.775: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.775: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.776: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.776: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.776: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.776: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.776: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.776: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.776: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.776: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.776: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.776: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.776: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.776: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.776: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.777: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Partial capture successful. Please touch the sensor again (7/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.777: Device reported enroll progress, reported 7 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.777: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.777: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.777: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.777: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.777: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.777: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.777: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.778: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.778: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.778: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.778: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.778: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.778: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.778: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.778: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.778: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.778: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.778: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.778: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.778: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.779: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Partial capture successful. Please touch the sensor again (8/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.779: Device reported enroll progress, reported 8 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.779: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.779: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.779: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.779: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.779: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.779: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.779: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.780: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.780: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.780: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.780: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.780: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.780: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.780: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.780: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.780: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.780: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.780: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.780: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.780: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.781: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Partial capture successful. Please touch the sensor again (9/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.781: Device reported enroll progress, reported 9 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.781: [egismoc] ENROLL_STATES entering state 8 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.781: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.781: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.781: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.781: [egismoc] ENROLL_STATES entering state 9 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.781: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.781: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.782: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.782: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.782: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.782: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.782: [egismoc] ENROLL_STATES entering state 10 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.782: Wait for finger on sensor 187s (process:2527): libfprint-device-DEBUG: 00:01:19.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.782: Finger on sensor callback 187s (process:2527): libfprint-device-DEBUG: 00:01:19.782: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.782: [egismoc] ENROLL_STATES entering state 11 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.782: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.782: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.782: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.782: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.783: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Read capture callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Response prefix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Response suffix valid: yes 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Partial capture successful. Please touch the sensor again (10/10) 187s (process:2527): libfprint-device-DEBUG: 00:01:19.783: Device reported enroll progress, reported 10 of 10 have been completed 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.783: [egismoc] ENROLL_STATES entering state 12 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.783: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.783: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.783: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.783: [egismoc] ENROLL_STATES entering state 13 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: New fingerprint ID: FP1-00000000-7-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.783: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.783: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.783: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] ENROLL_STATES entering state 14 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Task SSM next state callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] ENROLL_STATES entering state 15 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Enrollment was successful! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.784: Device reported enroll completion 187s (process:2527): libfprint-device-DEBUG: 00:01:19.784: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:2527): libfprint-device-DEBUG: 00:01:19.784: Print for finger FP_FINGER_RIGHT_INDEX enrolled 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] ENROLL_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.784: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.784: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: List 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] LIST_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.784: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.784: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.785: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.785: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: Device fingerprint 1: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: Device fingerprint 2: FP1-00000000-7-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: Number of currently enrolled fingerprints on the device is 2 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.785: [egismoc] LIST_STATES entering state 1 187s (process:2527): libfprint-device-DEBUG: 00:01:19.785: Device reported listing completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.785: [egismoc] LIST_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.785: Completing action FPI_DEVICE_ACTION_LIST in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.785: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: Delete 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.785: [egismoc] DELETE_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.785: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.785: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.785: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.786: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Device fingerprint 1: FP1-00000000-2-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Device fingerprint 2: FP1-00000000-7-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Number of currently enrolled fingerprints on the device is 2 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.786: [egismoc] DELETE_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Get delete command 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.786: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.786: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.786: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Delete callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Response prefix valid: yes 187s (process:2527): libfprint-device-DEBUG: 00:01:19.786: Device reported deletion completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.786: [egismoc] DELETE_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.786: Completing action FPI_DEVICE_ACTION_DELETE in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.786: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: List 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.786: [egismoc] LIST_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.786: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.786: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.787: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.787: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.787: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.787: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.787: Device fingerprint 1: FP1-00000000-7-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.787: Number of currently enrolled fingerprints on the device is 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.787: [egismoc] LIST_STATES entering state 1 187s (process:2527): libfprint-device-DEBUG: 00:01:19.787: Device reported listing completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.787: [egismoc] LIST_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.787: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.787: Completing action FPI_DEVICE_ACTION_LIST in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.787: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.787: Clear storage 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.787: [egismoc] DELETE_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.787: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.787: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.787: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.787: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Device fingerprint 1: FP1-00000000-7-00000000-nobody 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Number of currently enrolled fingerprints on the device is 1 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] DELETE_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Get delete command 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Delete callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Response prefix valid: yes 187s (process:2527): libfprint-device-DEBUG: 00:01:19.788: Device reported deletion completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] DELETE_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.788: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.788: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: List 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] LIST_STATES entering state 0 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Execute command and get response 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.788: Get check bytes 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] CMD_STATES entering state 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.788: [egismoc] CMD_STATES entering state 1 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.789: Command receive callback 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.789: [egismoc] CMD_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.789: List callback 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.789: Number of currently enrolled fingerprints on the device is 0 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.789: [egismoc] LIST_STATES entering state 1 187s (process:2527): libfprint-device-DEBUG: 00:01:19.789: Device reported listing completion 187s (process:2527): libfprint-SSM-DEBUG: 00:01:19.789: [egismoc] LIST_STATES completed successfully 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.789: Task SSM done 187s (process:2527): libfprint-device-DEBUG: 00:01:19.789: Completing action FPI_DEVICE_ACTION_LIST in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.789: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.789: Closing device 187s (process:2527): libfprint-egismoc-DEBUG: 00:01:19.789: Cancel 187s (process:2527): libfprint-device-DEBUG: 00:01:19.789: Device reported close completion 187s (process:2527): libfprint-device-DEBUG: 00:01:19.789: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:2527): libfprint-device-DEBUG: 00:01:19.789: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s listing - device should have prints 187s clear device storage 187s clear done 187s listing - device should be empty 187s enrolling 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 1, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 2, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 3, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 4, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 5, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 6, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 7, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 8, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 9, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 10, , None, None) 187s enroll done 187s listing - device should have 1 print 187s verifying 187s verify done 187s async identifying 187s indentification_done: 187s try to enroll duplicate 187s duplicate enroll attempt done 187s listing - device should still only have 1 print 187s enroll new finger 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 1, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 2, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 3, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 4, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 5, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 6, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 7, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 8, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 9, , None, None) 187s finger status: 187s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa9b0e3c0 (FpiDeviceEgisMoc at 0x3609950)>, 10, , None, None) 187s enroll new finger done 187s listing - device should have 2 prints 187s deleting first print 187s delete done 187s listing - device should only have second print 187s clear device storage 187s clear done 187s listing - device should be empty 187s ** (umockdev-run:2523): DEBUG: 00:01:19.801: umockdev.vala:154: Removing test bed /tmp/umockdev.QW6B22 187s (umockdev-run:2523): GLib-DEBUG: 00:01:19.803: unsetenv() is not thread-safe and should not be used after threads are created 187s PASS: libfprint-2/driver-egismoc-05a1.test 187s Running test: libfprint-2/driver-focaltech_moc.test 187s ** (umockdev-run:2535): DEBUG: 00:01:19.835: umockdev.vala:127: Created udev test bed /tmp/umockdev.21RI22 187s ** (umockdev-run:2535): DEBUG: 00:01:19.835: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 187s ** (umockdev-run:2535): DEBUG: 00:01:19.839: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 187s ** (umockdev-run:2535): DEBUG: 00:01:19.840: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.21RI22/dev/bus/usb/003/006 187s ** (umockdev-run:2535): DEBUG: 00:01:19.840: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 187s ** (umockdev-run:2535): DEBUG: 00:01:19.844: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 187s ** (umockdev-run:2535): DEBUG: 00:01:19.845: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.21RI22/dev/bus/usb/003/002 187s ** (umockdev-run:2535): DEBUG: 00:01:19.845: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 187s ** (umockdev-run:2535): DEBUG: 00:01:19.849: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 187s ** (umockdev-run:2535): DEBUG: 00:01:19.850: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.21RI22/dev/bus/usb/003/001 187s ** (umockdev-run:2535): DEBUG: 00:01:19.850: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 187s ** (umockdev-run:2535): DEBUG: 00:01:19.852: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 187s ** (umockdev-run:2535): DEBUG: 00:01:19.853: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4 187s ** (umockdev-run:2535): DEBUG: 00:01:19.853: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 187s (process:2539): libfprint-context-DEBUG: 00:01:19.911: Initializing FpContext (libfprint version 1.94.8+tod1) 187s (process:2539): libfprint-tod-DEBUG: 00:01:19.911: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 187s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:19.912: 72833842: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1849 187s (process:2539): libfprint-context-DEBUG: 00:01:19.912: No driver found for USB device 05E3:0608 187s (process:2539): libfprint-context-DEBUG: 00:01:19.912: No driver found for USB device 1D6B:0002 187s (process:2539): libfprint-device-DEBUG: 00:01:19.912: Device reported probe completion 187s (process:2539): libfprint-device-DEBUG: 00:01:19.912: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s (process:2539): libfprint-device-DEBUG: 00:01:19.912: Not updating temperature model, device can run continuously! 187s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 187s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 187s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:19.913: class:dc, subclass:a0, protocol:b0 187s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:19.913: bytes size:0 187s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:19.913: 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 187s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:19.913: bytes size:0 187s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:19.913: 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 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.913: [focaltech_moc] DEV_INIT_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.913: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.914: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 187s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:19.914: focaltechmoc enroll_times: 10 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.914: [focaltech_moc] DEV_INIT_STATES entering state 1 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.914: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.914: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.914: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.914: [focaltech_moc] DEV_INIT_STATES completed successfully 187s (process:2539): libfprint-device-DEBUG: 00:01:19.914: Device reported open completion 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.914: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 187s (process:2539): libfprint-device-DEBUG: 00:01:19.914: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s (process:2539): libfprint-device-DEBUG: 00:01:19.914: Not updating temperature model, device can run continuously! 187s (process:2539): libfprint-device-DEBUG: 00:01:19.915: Not updating temperature model, device can run continuously! 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.915: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.915: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.915: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.915: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.915: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.916: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.916: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.916: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.916: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.916: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.916: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.916: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.916: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.917: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.917: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 187s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:19.917: focaltechmoc user id: FP1-00000000-0-00000000-nobody 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.917: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.917: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.917: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.917: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.917: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 187s (process:2539): libfprint-SSM-DEBUG: 00:01:19.917: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:19.967: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:19.968: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:19.968: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:19.968: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:19.969: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.019: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.019: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.019: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.019: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.019: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.069: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.069: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.070: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.070: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.070: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.120: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.120: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.121: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.121: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.121: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.171: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.171: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.171: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.172: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.172: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.222: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.222: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.222: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.223: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.223: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.223: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.223: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-device-DEBUG: 00:01:20.223: Device reported enroll progress, reported 1 of 10 have been completed 188s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:20.223: focaltechmoc remain: 9 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.223: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.223: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.224: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.224: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.224: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.224: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.274: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.274: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.274: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.275: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.275: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.325: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.325: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.325: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.325: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.325: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.375: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.376: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.376: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.376: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.376: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.426: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.426: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.427: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.427: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.427: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.477: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.477: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.478: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.478: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.478: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.478: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.478: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-device-DEBUG: 00:01:20.479: Device reported enroll progress, reported 2 of 10 have been completed 188s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:20.479: focaltechmoc remain: 8 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.479: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.479: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.479: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.479: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.479: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.479: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.530: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.530: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.530: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.530: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.530: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.530: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.531: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-device-DEBUG: 00:01:20.531: Device reported enroll progress, reported 3 of 10 have been completed 188s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:20.531: focaltechmoc remain: 7 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.531: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.531: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.531: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.531: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.532: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.532: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.582: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.582: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.582: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.582: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.582: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.633: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.633: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.633: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.633: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.633: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.683: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.683: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.684: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.684: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.684: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.734: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.734: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.734: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.735: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.735: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.785: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.785: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.785: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.785: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.785: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.786: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.786: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-device-DEBUG: 00:01:20.786: Device reported enroll progress, reported 4 of 10 have been completed 188s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:20.786: focaltechmoc remain: 6 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.786: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.786: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.786: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.787: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.787: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.787: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.837: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.837: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.837: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.838: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.838: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.888: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.888: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.888: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.888: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.888: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.939: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.939: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.939: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.939: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.939: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.939: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.940: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-device-DEBUG: 00:01:20.940: Device reported enroll progress, reported 5 of 10 have been completed 188s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:20.940: focaltechmoc remain: 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.940: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.940: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.940: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.940: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.941: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 188s (process:2539): libfprint-SSM-DEBUG: 00:01:20.941: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:20.991: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:20.991: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:20.991: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:20.992: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:20.992: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.042: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.042: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.042: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.042: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.042: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.092: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.092: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.093: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.093: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.093: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.144: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.144: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.144: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.144: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.144: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.145: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.145: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-device-DEBUG: 00:01:21.145: Device reported enroll progress, reported 6 of 10 have been completed 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.145: focaltechmoc remain: 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.145: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.145: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.146: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.146: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.146: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.146: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.146: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.146: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-device-DEBUG: 00:01:21.147: Device reported enroll progress, reported 6 of 10 have been completed 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.147: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.147: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.147: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.147: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.148: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.148: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.198: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.198: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.198: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.199: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.199: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.249: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.249: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.249: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.249: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.249: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.299: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.299: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.300: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.300: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.300: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.350: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.350: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.351: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.351: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.351: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.351: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.351: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-device-DEBUG: 00:01:21.352: Device reported enroll progress, reported 7 of 10 have been completed 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.352: focaltechmoc remain: 3 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.352: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.352: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.352: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.352: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.353: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.353: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.403: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.403: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.403: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.403: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.403: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.453: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.453: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.454: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.454: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.454: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.454: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.454: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-device-DEBUG: 00:01:21.454: Device reported enroll progress, reported 8 of 10 have been completed 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.455: focaltechmoc remain: 2 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.455: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.455: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.455: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.455: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.455: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.455: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.505: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.505: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.505: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.506: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.506: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.506: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.506: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-device-DEBUG: 00:01:21.506: Device reported enroll progress, reported 9 of 10 have been completed 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.506: focaltechmoc remain: 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.506: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.506: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.506: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.506: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.507: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.507: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.557: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.557: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.557: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.557: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.557: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.558: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.558: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-device-DEBUG: 00:01:21.558: Device reported enroll progress, reported 10 of 10 have been completed 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.558: focaltechmoc remain: 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.558: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.558: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.558: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.558: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.559: focaltech_moc_commit_cb success 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.559: Enrollment was successful! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.559: Device reported enroll completion 189s (process:2539): libfprint-device-DEBUG: 00:01:21.559: Print for finger FP_FINGER_UNKNOWN enrolled 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-device-DEBUG: 00:01:21.559: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.559: Not updating temperature model, device can run continuously! 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.559: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.560: focaltechmoc add slot: 0 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.560: FP1-00000000-0-00000000-nobody 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 189s (process:2539): libfprint-device-DEBUG: 00:01:21.560: Device reported listing completion 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-device-DEBUG: 00:01:21.560: Completing action FPI_DEVICE_ACTION_LIST in idle! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.560: Not updating temperature model, device can run continuously! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.560: Not updating temperature model, device can run continuously! 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.560: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.561: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.561: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.561: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.561: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.561: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.561: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.562: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.612: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.612: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.612: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.612: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.612: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.662: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.662: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.662: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.663: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.663: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.713: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.713: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.713: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.713: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.713: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.763: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.763: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.764: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.764: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.764: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.764: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.764: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.764: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.764: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.765: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.765: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-device-DEBUG: 00:01:21.765: Device reported verify result 189s (process:2539): libfprint-device-DEBUG: 00:01:21.765: Device reported verify completion 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.765: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.765: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-device-DEBUG: 00:01:21.765: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.765: Not updating temperature model, device can run continuously! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.766: Not updating temperature model, device can run continuously! 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.766: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.766: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.766: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.766: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.766: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.766: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.766: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.767: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.767: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.817: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.817: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.817: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.817: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.818: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.868: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.868: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.868: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.868: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.868: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.868: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.869: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.869: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.869: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.869: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.869: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-device-DEBUG: 00:01:21.869: Device reported identify result 189s (process:2539): libfprint-device-DEBUG: 00:01:21.869: Device reported identify completion 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.869: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.869: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-device-DEBUG: 00:01:21.869: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.869: Not updating temperature model, device can run continuously! 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.870: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.870: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.870: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.870: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.870: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.871: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.871: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.871: focaltechmoc add slot: 0 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.871: FP1-00000000-0-00000000-nobody 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.871: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.871: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.871: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.871: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.872: delete slot 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 189s (process:2539): libfprint-device-DEBUG: 00:01:21.872: Device reported deletion completion 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 189s (process:2539): libfprint-device-DEBUG: 00:01:21.872: Completing action FPI_DEVICE_ACTION_DELETE in idle! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.872: Not updating temperature model, device can run continuously! 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.872: Focaltechmoc dev_exit 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] DEV_EXIT_STATES entering state 0 189s (process:2539): libfprint-SSM-DEBUG: 00:01:21.872: [focaltech_moc] DEV_EXIT_STATES completed successfully 189s (process:2539): libfprint-focaltech_moc-DEBUG: 00:01:21.872: class:dc, subclass:a0, protocol:b0 189s (process:2539): libfprint-device-DEBUG: 00:01:21.872: Device reported close completion 189s (process:2539): libfprint-device-DEBUG: 00:01:21.873: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:2539): libfprint-device-DEBUG: 00:01:21.873: Not updating temperature model, device can run continuously! 189s enrolling 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 1, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 2, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 3, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 4, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 5, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 6, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 7, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 8, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 9, None, None, None) 189s finger status: 189s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff8c709c40 (FpiDeviceFocaltechMoc at 0x3360d10)>, 10, None, None, None) 189s enroll done 189s listing 189s listing done 189s verifying 189s verify done 189s async identifying 189s indentification_done: 189s deleting 189s delete done 189s ** (umockdev-run:2535): DEBUG: 00:01:21.885: umockdev.vala:154: Removing test bed /tmp/umockdev.21RI22 189s (umockdev-run:2535): GLib-DEBUG: 00:01:21.889: unsetenv() is not thread-safe and should not be used after threads are created 189s PASS: libfprint-2/driver-focaltech_moc.test 189s Running test: libfprint-2/fpi-assembling.test 189s TAP version 14 189s # random seed: R02S10c18b7f69899bb8aa41c4b25baa80aa 189s 1..1 189s # Start of assembling tests 189s 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) 189s Bail out! 189s ** 189s libfprint:ERROR:../tests/test-fpi-assembling.c:76:test_frame_assembling: assertion failed (cairo_image_surface_get_format (img) == CAIRO_FORMAT_RGB24): (0 == 1) 190s FAIL: libfprint-2/fpi-assembling.test (Child process killed by signal 6) 190s Running test: libfprint-2/driver-elanmoc.test 190s ** (umockdev-run:2555): DEBUG: 00:01:22.737: umockdev.vala:127: Created udev test bed /tmp/umockdev.4GUD22 190s ** (umockdev-run:2555): DEBUG: 00:01:22.737: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 190s ** (umockdev-run:2555): DEBUG: 00:01:22.738: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 190s ** (umockdev-run:2555): DEBUG: 00:01:22.739: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4GUD22/dev/bus/usb/001/003 190s ** (umockdev-run:2555): DEBUG: 00:01:22.739: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 190s ** (umockdev-run:2555): DEBUG: 00:01:22.740: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 190s ** (umockdev-run:2555): DEBUG: 00:01:22.741: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4GUD22/dev/bus/usb/001/001 190s ** (umockdev-run:2555): DEBUG: 00:01:22.741: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 190s ** (umockdev-run:2555): DEBUG: 00:01:22.742: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 190s (process:2559): libfprint-context-DEBUG: 00:01:22.799: Initializing FpContext (libfprint version 1.94.8+tod1) 190s (process:2559): libfprint-tod-DEBUG: 00:01:22.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 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.800: 75722242: ../libfprint/drivers/elanmoc/elanmoc.c:1151 190s (process:2559): libfprint-context-DEBUG: 00:01:22.800: No driver found for USB device 1D6B:0002 190s (process:2559): libfprint-device-DEBUG: 00:01:22.801: Device reported probe completion 190s (process:2559): libfprint-device-DEBUG: 00:01:22.801: Completing action FPI_DEVICE_ACTION_PROBE in idle! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.801: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.802: [elanmoc] DEV_INIT_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.802: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.802: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.802: [elanmoc] DEV_INIT_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.802: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.802: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.802: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.803: [elanmoc] DEV_INIT_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.803: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.803: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.803: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.803: elanmoc FW Version 8004 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.803: [elanmoc] DEV_INIT_STATES entering state 3 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.803: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.803: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.803: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.804: elanmoc last_read DIM 0x57(87) 0x6B(107) 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.804: [elanmoc] DEV_INIT_STATES entering state 4 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.804: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.804: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.804: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.804: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.804: [elanmoc] DEV_INIT_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.804: Device reported open completion 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.804: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.804: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.804: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.805: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.805: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.805: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.805: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.805: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.805: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.805: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.806: ##### Re-Enrollment Case! ##### 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.806: Device reported enroll progress, reported 1 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.806: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.807: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.807: Device reported enroll progress, reported 2 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.807: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.807: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.807: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.807: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.808: Device reported enroll progress, reported 3 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.808: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.808: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.808: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.808: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.808: Device reported enroll progress, reported 4 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.808: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.808: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.809: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.809: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.809: Device reported enroll progress, reported 5 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.809: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.809: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.810: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.810: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.810: Device reported enroll progress, reported 6 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.810: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.810: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.810: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.811: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.811: Device reported enroll progress, reported 7 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.811: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.811: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.811: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.811: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.811: Device reported enroll progress, reported 7 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.812: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.812: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.812: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.812: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.812: Device reported enroll progress, reported 8 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.812: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.812: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.812: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.812: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.813: Device reported enroll progress, reported 8 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.813: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.813: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.813: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.813: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.813: Device reported enroll progress, reported 9 of 9 have been completed 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.813: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.813: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.814: elanmoc_commit_cb success 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.814: Enrollment was successful! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.814: Device reported enroll completion 190s (process:2559): libfprint-device-DEBUG: 00:01:22.814: Print for finger FP_FINGER_UNKNOWN enrolled 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.814: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.814: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] MOC_LIST_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.814: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.814: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.815: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.815: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.815: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.815: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.815: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.815: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.815: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.815: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.816: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.816: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.816: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.816: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.816: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.816: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.817: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.817: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.817: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.817: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.817: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.817: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.817: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.817: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.818: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.818: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.818: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.818: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.818: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.818: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.818: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.818: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.819: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.819: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.819: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.819: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.819: [elanmoc] MOC_LIST_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.819: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.819: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.819: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.820: Device reported listing completion 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] MOC_LIST_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.820: Completing action FPI_DEVICE_ACTION_LIST in idle! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.820: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.820: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] IDENTIFY_NUM_STATES entering state 0 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.820: elanmoc elan_identify_run_state 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.820: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] IDENTIFY_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.820: elanmoc elan_identify_run_state 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.820: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.820: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.821: Verify was successful! for user: 0 mesg_code: 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.821: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.821: [elanmoc] IDENTIFY_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.821: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.821: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.821: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 190s (process:2559): libfprint-device-DEBUG: 00:01:22.821: Device reported verify result 190s (process:2559): libfprint-device-DEBUG: 00:01:22.821: Device reported verify completion 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.821: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.821: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.821: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.822: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.822: [elanmoc] IDENTIFY_NUM_STATES entering state 0 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.822: elanmoc elan_identify_run_state 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.822: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.822: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.822: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.822: [elanmoc] IDENTIFY_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.822: elanmoc elan_identify_run_state 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.822: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.822: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.822: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.822: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.823: Verify was successful! for user: 0 mesg_code: 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.823: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.823: [elanmoc] IDENTIFY_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.823: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.823: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.823: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 190s (process:2559): libfprint-device-DEBUG: 00:01:22.823: Device reported identify result 190s (process:2559): libfprint-device-DEBUG: 00:01:22.823: Device reported identify completion 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.823: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.823: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.823: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.823: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.823: [elanmoc] DELETE_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.823: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.824: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-device-DEBUG: 00:01:22.824: Device reported deletion completion 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.824: [elanmoc] DELETE_NUM_STATES completed successfully 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.824: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.824: Completing action FPI_DEVICE_ACTION_DELETE in idle! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.824: Not updating temperature model, device can run continuously! 190s (process:2559): libfprint-elanmoc-DEBUG: 00:01:22.824: Elanmoc dev_exit 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.824: [elanmoc] DEV_EXIT_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.824: [elanmoc] FP_CMD_NUM_STATES entering state 0 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.824: [elanmoc] FP_CMD_NUM_STATES entering state 1 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.824: [elanmoc] DEV_EXIT_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.824: Device reported close completion 190s (process:2559): libfprint-SSM-DEBUG: 00:01:22.824: [elanmoc] FP_CMD_NUM_STATES completed successfully 190s (process:2559): libfprint-device-DEBUG: 00:01:22.824: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s (process:2559): libfprint-device-DEBUG: 00:01:22.824: Not updating temperature model, device can run continuously! 190s enrolling 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 1, None, None, None) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 2, None, None, None) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 3, None, None, None) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 4, None, None, None) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 5, None, None, None) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 6, None, None, None) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 7, None, None, None) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 8, None, None, None) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 190s finger status: 190s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff84f09f00 (FpiDeviceElanmoc at 0x257e620)>, 9, None, None, None) 190s enroll done 190s listing 190s listing done 190s verifying 190s verify done 190s async identifying 190s indentification_done: 190s deleting 190s delete done 190s ** (umockdev-run:2555): DEBUG: 00:01:22.835: umockdev.vala:154: Removing test bed /tmp/umockdev.4GUD22 190s (umockdev-run:2555): GLib-DEBUG: 00:01:22.837: unsetenv() is not thread-safe and should not be used after threads are created 190s PASS: libfprint-2/driver-elanmoc.test 190s Running test: libfprint-2/driver-egismoc-0587.test 190s ** (umockdev-run:2567): DEBUG: 00:01:22.870: umockdev.vala:127: Created udev test bed /tmp/umockdev.WY2G22 190s ** (umockdev-run:2567): DEBUG: 00:01:22.870: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 190s ** (umockdev-run:2567): DEBUG: 00:01:22.872: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 190s ** (umockdev-run:2567): DEBUG: 00:01:22.873: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WY2G22/dev/bus/usb/003/009 190s ** (umockdev-run:2567): DEBUG: 00:01:22.873: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 190s ** (umockdev-run:2567): DEBUG: 00:01:22.874: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 190s ** (umockdev-run:2567): DEBUG: 00:01:22.875: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WY2G22/dev/bus/usb/003/001 190s ** (umockdev-run:2567): DEBUG: 00:01:22.876: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 190s ** (umockdev-run:2567): DEBUG: 00:01:22.876: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 190s (process:2571): libfprint-context-DEBUG: 00:01:22.943: Initializing FpContext (libfprint version 1.94.8+tod1) 190s (process:2571): libfprint-tod-DEBUG: 00:01:22.943: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.944: 75865719: ../libfprint/drivers/egismoc/egismoc.c:1597 190s (process:2571): libfprint-context-DEBUG: 00:01:22.944: No driver found for USB device 1D6B:0002 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.944: egismoc_probe enter --> 190s (process:2571): libfprint-device-DEBUG: 00:01:22.945: Device reported probe completion 190s (process:2571): libfprint-device-DEBUG: 00:01:22.945: Completing action FPI_DEVICE_ACTION_PROBE in idle! 190s (process:2571): libfprint-device-DEBUG: 00:01:22.945: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.945: Opening device 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.945: [egismoc] DEV_INIT_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.946: [egismoc] DEV_INIT_STATES entering state 1 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.946: [egismoc] DEV_INIT_STATES entering state 2 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.946: [egismoc] DEV_INIT_STATES entering state 3 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.947: [egismoc] DEV_INIT_STATES entering state 4 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.947: [egismoc] DEV_INIT_STATES entering state 5 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.947: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.947: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.947: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.947: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.947: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.947: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.947: Firmware version callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.947: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.947: Device firmware version is 9050.6.4.67 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.947: [egismoc] DEV_INIT_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.947: Task SSM done 190s (process:2571): libfprint-device-DEBUG: 00:01:22.947: Device reported open completion 190s (process:2571): libfprint-device-DEBUG: 00:01:22.947: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:2571): libfprint-device-DEBUG: 00:01:22.947: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: List 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.948: [egismoc] LIST_STATES entering state 0 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.948: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.948: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.948: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: List callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Device fingerprint 1: FP1-00000000-2-00000000-nobody 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Number of currently enrolled fingerprints on the device is 1 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.948: [egismoc] LIST_STATES entering state 1 190s (process:2571): libfprint-device-DEBUG: 00:01:22.948: Device reported listing completion 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.948: [egismoc] LIST_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Task SSM done 190s (process:2571): libfprint-device-DEBUG: 00:01:22.948: Completing action FPI_DEVICE_ACTION_LIST in idle! 190s (process:2571): libfprint-device-DEBUG: 00:01:22.948: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Clear storage 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.948: [egismoc] DELETE_STATES entering state 0 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.948: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.948: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: List callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Device fingerprint 1: FP1-00000000-2-00000000-nobody 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Number of currently enrolled fingerprints on the device is 1 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] DELETE_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Get delete command 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Delete callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Response prefix valid: yes 190s (process:2571): libfprint-device-DEBUG: 00:01:22.949: Device reported deletion completion 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] DELETE_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Task SSM done 190s (process:2571): libfprint-device-DEBUG: 00:01:22.949: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 190s (process:2571): libfprint-device-DEBUG: 00:01:22.949: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: List 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] LIST_STATES entering state 0 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.949: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.949: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.950: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.950: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.950: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.950: List callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.950: Number of currently enrolled fingerprints on the device is 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.950: [egismoc] LIST_STATES entering state 1 190s (process:2571): libfprint-device-DEBUG: 00:01:22.950: Device reported listing completion 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.950: [egismoc] LIST_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.950: Task SSM done 190s (process:2571): libfprint-device-DEBUG: 00:01:22.950: Completing action FPI_DEVICE_ACTION_LIST in idle! 190s (process:2571): libfprint-device-DEBUG: 00:01:22.950: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:2571): libfprint-device-DEBUG: 00:01:22.950: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.950: Enroll 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.950: [egismoc] ENROLL_STATES entering state 0 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.950: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.950: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.950: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.950: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: List callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: Number of currently enrolled fingerprints on the device is 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] ENROLL_STATES entering state 1 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] ENROLL_STATES entering state 2 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] ENROLL_STATES entering state 3 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.951: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.951: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.952: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.952: [egismoc] ENROLL_STATES entering state 4 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.952: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.952: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.952: [egismoc] ENROLL_STATES entering state 5 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.952: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.952: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.952: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.952: [egismoc] ENROLL_STATES entering state 6 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Get check command 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.952: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.953: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.953: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.953: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.953: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.953: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.953: Enroll check callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.953: Response suffix valid: yes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.953: [egismoc] ENROLL_STATES entering state 7 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.953: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.953: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.953: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.953: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.954: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.954: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.954: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.954: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.954: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.954: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.954: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.954: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.954: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.954: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.954: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.954: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.954: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.954: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.954: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.954: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.955: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.955: [egismoc] ENROLL_STATES entering state 10 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.955: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.955: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.955: [egismoc] ENROLL_STATES entering state 11 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.955: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.955: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.955: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Read capture callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Response prefix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Partial capture successful. Please touch the sensor again (1/20) 190s (process:2571): libfprint-device-DEBUG: 00:01:22.955: Device reported enroll progress, reported 1 of 20 have been completed 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.955: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.955: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.955: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.956: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.956: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.956: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.956: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.956: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.956: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.956: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.956: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.956: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.956: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.956: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.956: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.956: [egismoc] ENROLL_STATES entering state 10 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.956: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.956: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.957: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.957: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.957: [egismoc] ENROLL_STATES entering state 11 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.957: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.957: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.957: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.957: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.957: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.957: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.957: Read capture callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.957: Response prefix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.957: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.957: Partial capture successful. Please touch the sensor again (2/20) 190s (process:2571): libfprint-device-DEBUG: 00:01:22.957: Device reported enroll progress, reported 2 of 20 have been completed 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.958: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.958: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.958: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.958: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.958: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.958: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.958: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.958: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.958: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.958: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.958: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.958: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.958: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.959: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.959: [egismoc] ENROLL_STATES entering state 10 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.959: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.959: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.959: [egismoc] ENROLL_STATES entering state 11 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.959: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.959: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.959: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Read capture callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Response prefix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Partial capture successful. Please touch the sensor again (3/20) 190s (process:2571): libfprint-device-DEBUG: 00:01:22.959: Device reported enroll progress, reported 3 of 20 have been completed 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.959: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.959: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.959: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.960: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.960: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.960: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.960: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.960: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.960: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.960: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.960: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.960: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.960: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.960: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.960: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.960: [egismoc] ENROLL_STATES entering state 10 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.960: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.960: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.961: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.961: [egismoc] ENROLL_STATES entering state 11 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.961: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.961: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.961: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Read capture callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Response prefix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Partial capture successful. Please touch the sensor again (4/20) 190s (process:2571): libfprint-device-DEBUG: 00:01:22.961: Device reported enroll progress, reported 4 of 20 have been completed 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.961: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.961: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.961: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.961: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.962: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.962: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.962: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.962: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.962: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.962: [egismoc] ENROLL_STATES entering state 10 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.962: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.962: [egismoc] ENROLL_STATES entering state 11 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.962: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.962: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.963: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.963: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Read capture callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Response prefix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Partial capture successful. Please touch the sensor again (5/20) 190s (process:2571): libfprint-device-DEBUG: 00:01:22.963: Device reported enroll progress, reported 5 of 20 have been completed 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.963: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.963: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.963: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.963: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.963: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.963: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.963: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.964: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.964: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.964: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.964: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.964: [egismoc] ENROLL_STATES entering state 10 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.964: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.964: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.964: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.964: [egismoc] ENROLL_STATES entering state 11 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.964: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.964: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.964: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.964: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.965: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Read capture callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Response prefix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Partial capture successful. Please touch the sensor again (6/20) 190s (process:2571): libfprint-device-DEBUG: 00:01:22.965: Device reported enroll progress, reported 6 of 20 have been completed 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.965: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.965: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.965: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.965: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.965: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.965: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.965: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.965: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.966: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.966: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.966: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.966: [egismoc] ENROLL_STATES entering state 10 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.966: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.966: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.966: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.966: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.966: [egismoc] ENROLL_STATES entering state 11 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.966: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.966: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.966: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.966: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.966: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.967: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Read capture callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Response prefix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Partial capture successful. Please touch the sensor again (7/20) 190s (process:2571): libfprint-device-DEBUG: 00:01:22.967: Device reported enroll progress, reported 7 of 20 have been completed 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.967: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.967: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.967: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.967: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.967: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.967: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.967: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.967: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.968: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.968: [egismoc] ENROLL_STATES entering state 10 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Wait for finger on sensor 190s (process:2571): libfprint-device-DEBUG: 00:01:22.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Finger on sensor callback 190s (process:2571): libfprint-device-DEBUG: 00:01:22.968: Device reported finger status change: FP_FINGER_STATUS_PRESENT 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.968: [egismoc] ENROLL_STATES entering state 11 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.968: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.968: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.968: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Read capture callback 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Response prefix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Response suffix valid: yes 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Partial capture successful. Please touch the sensor again (8/20) 190s (process:2571): libfprint-device-DEBUG: 00:01:22.968: Device reported enroll progress, reported 8 of 20 have been completed 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.968: [egismoc] ENROLL_STATES entering state 8 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.968: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.968: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.969: [egismoc] CMD_STATES entering state 1 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.969: Command receive callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.969: [egismoc] CMD_STATES completed successfully 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.969: Task SSM next state callback 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.969: [egismoc] ENROLL_STATES entering state 9 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.969: Execute command and get response 190s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.969: Get check bytes 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.969: [egismoc] CMD_STATES entering state 0 190s (process:2571): libfprint-SSM-DEBUG: 00:01:22.969: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.970: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.970: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.970: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.970: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.970: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.970: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.970: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.970: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.970: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.970: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.970: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.970: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.970: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.971: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Partial capture successful. Please touch the sensor again (9/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.971: Device reported enroll progress, reported 9 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.971: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.971: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.971: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.971: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.971: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.971: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.971: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.971: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.972: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.972: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.972: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.972: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.972: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.972: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.972: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Response suffix valid: NO 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Response suffix valid: yes 191s (process:2571): libfprint-device-DEBUG: 00:01:22.972: Device reported enroll progress, reported 9 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.972: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.972: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.972: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.973: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.973: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.973: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.973: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.973: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.973: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.973: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.973: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.973: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.973: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.973: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.973: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.973: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.973: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.974: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.974: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.974: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.974: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.974: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Partial capture successful. Please touch the sensor again (10/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.974: Device reported enroll progress, reported 10 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.974: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.974: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.974: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.975: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.975: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.975: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.975: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.975: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.975: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.975: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.975: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.975: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.975: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.975: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.975: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.975: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.975: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.976: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.976: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.976: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.976: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.976: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Response suffix valid: NO 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Response suffix valid: yes 191s (process:2571): libfprint-device-DEBUG: 00:01:22.976: Device reported enroll progress, reported 10 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.976: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.976: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.976: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.976: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.977: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.977: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.977: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.977: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.977: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.977: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.977: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.977: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.977: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.977: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.977: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.977: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.977: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.977: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.978: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.978: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.978: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.978: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.978: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Partial capture successful. Please touch the sensor again (11/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.978: Device reported enroll progress, reported 11 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.978: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.978: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.978: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.979: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.979: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.979: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.979: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.979: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.979: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.979: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.979: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.979: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.979: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.979: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.979: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.979: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.979: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.980: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.980: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.980: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.980: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.980: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Partial capture successful. Please touch the sensor again (12/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.980: Device reported enroll progress, reported 12 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.980: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.980: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.980: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.981: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.981: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.981: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.981: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.981: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.981: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.981: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.981: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.981: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.981: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.981: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.981: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.981: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.981: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.982: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.982: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.982: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.982: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.982: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Partial capture successful. Please touch the sensor again (13/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.982: Device reported enroll progress, reported 13 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.982: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.982: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.982: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.983: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.983: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.983: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.983: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.983: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.983: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.983: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.983: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.983: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.983: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.983: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.983: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.983: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.983: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.984: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.984: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.984: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.984: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.984: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Partial capture successful. Please touch the sensor again (14/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.984: Device reported enroll progress, reported 14 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.984: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.984: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.984: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.985: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.985: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.985: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.985: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.985: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.985: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.985: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.985: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.985: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.985: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.985: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.985: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.985: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.985: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.986: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.986: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.986: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.986: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.986: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Partial capture successful. Please touch the sensor again (15/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.986: Device reported enroll progress, reported 15 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.986: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.986: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.986: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.987: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.987: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.987: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.987: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.987: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.987: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.987: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.987: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.987: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.987: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.987: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.987: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.987: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.987: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.988: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.988: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.988: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.988: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.988: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.988: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Partial capture successful. Please touch the sensor again (16/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.988: Device reported enroll progress, reported 16 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.988: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.988: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.988: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.989: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.989: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.989: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.989: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.989: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.989: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.989: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.989: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.989: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.990: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.990: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.990: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.990: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.990: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.990: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.990: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Partial capture successful. Please touch the sensor again (17/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.990: Device reported enroll progress, reported 17 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.990: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.990: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.990: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.991: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.991: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.991: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.991: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.991: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.991: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.991: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.991: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.991: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.992: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.992: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.992: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.992: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.992: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.992: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.992: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Partial capture successful. Please touch the sensor again (18/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.992: Device reported enroll progress, reported 18 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.992: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.992: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.992: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.993: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.993: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.993: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.993: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.993: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.993: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.993: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.993: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.993: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.993: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.993: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.993: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.993: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.993: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.993: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.994: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.994: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.994: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.994: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.994: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Partial capture successful. Please touch the sensor again (19/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.994: Device reported enroll progress, reported 19 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.994: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.994: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.994: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.994: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.995: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.995: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.995: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.995: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.995: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.995: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.995: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.995: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.995: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.995: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.995: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.995: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.995: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:22.995: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:22.996: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.996: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.996: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.996: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.996: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Partial capture successful. Please touch the sensor again (20/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:22.996: Device reported enroll progress, reported 20 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.996: [egismoc] ENROLL_STATES entering state 12 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.996: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.996: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.996: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.997: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.997: [egismoc] ENROLL_STATES entering state 13 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: New fingerprint ID: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.997: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.997: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.997: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.997: [egismoc] ENROLL_STATES entering state 14 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.997: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.997: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.997: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] ENROLL_STATES entering state 15 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Enrollment was successful! 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Device reported enroll completion 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Print for finger FP_FINGER_LEFT_INDEX enrolled 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] ENROLL_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: List 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] LIST_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Device fingerprint 1: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Number of currently enrolled fingerprints on the device is 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] LIST_STATES entering state 1 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Device reported listing completion 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] LIST_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Completing action FPI_DEVICE_ACTION_LIST in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-device-DEBUG: 00:01:22.998: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Identify or Verify 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] IDENTIFY_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.998: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.998: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Device fingerprint 1: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Number of currently enrolled fingerprints on the device is 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] IDENTIFY_STATES entering state 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] IDENTIFY_STATES entering state 2 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] IDENTIFY_STATES entering state 3 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:22.999: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:22.999: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.000: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.000: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.000: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.000: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.000: [egismoc] IDENTIFY_STATES entering state 4 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.000: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.000: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.000: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.000: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.000: [egismoc] IDENTIFY_STATES entering state 5 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.000: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.000: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.000: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.000: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.001: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.001: [egismoc] IDENTIFY_STATES entering state 6 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Get check command 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.001: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.001: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.001: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Identify check callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Identify successful for: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Verifying against: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-device-DEBUG: 00:01:23.001: Device reported verify result 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.001: [egismoc] IDENTIFY_STATES entering state 7 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.001: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.001: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.001: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] IDENTIFY_STATES entering state 8 191s (process:2571): libfprint-device-DEBUG: 00:01:23.002: Device reported verify completion 191s (process:2571): libfprint-device-DEBUG: 00:01:23.002: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] IDENTIFY_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.002: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.002: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-device-DEBUG: 00:01:23.002: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Identify or Verify 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] IDENTIFY_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Device fingerprint 1: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Number of currently enrolled fingerprints on the device is 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] IDENTIFY_STATES entering state 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] IDENTIFY_STATES entering state 2 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.002: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.002: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.003: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.003: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.003: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.003: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.003: [egismoc] IDENTIFY_STATES entering state 3 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.003: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.003: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.003: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.003: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.003: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.003: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.003: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.003: [egismoc] IDENTIFY_STATES entering state 4 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.004: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.004: [egismoc] IDENTIFY_STATES entering state 5 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.004: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.004: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.004: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.004: [egismoc] IDENTIFY_STATES entering state 6 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Get check command 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.004: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.004: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.005: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.005: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Identify check callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Identify successful for: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-device-DEBUG: 00:01:23.005: Device reported identify result 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.005: [egismoc] IDENTIFY_STATES entering state 7 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.005: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.005: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.005: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.005: [egismoc] IDENTIFY_STATES entering state 8 191s (process:2571): libfprint-device-DEBUG: 00:01:23.005: Device reported identify completion 191s (process:2571): libfprint-device-DEBUG: 00:01:23.005: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.005: [egismoc] IDENTIFY_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.005: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.005: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.005: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-device-DEBUG: 00:01:23.006: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: Enroll 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.006: [egismoc] ENROLL_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.006: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.006: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.006: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: Device fingerprint 1: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: Number of currently enrolled fingerprints on the device is 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.006: [egismoc] ENROLL_STATES entering state 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.006: [egismoc] ENROLL_STATES entering state 2 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.006: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.006: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.006: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.007: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.007: [egismoc] ENROLL_STATES entering state 3 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.007: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.007: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.007: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.007: [egismoc] ENROLL_STATES entering state 4 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.007: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.007: [egismoc] ENROLL_STATES entering state 5 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.007: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.007: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.008: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.008: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.008: [egismoc] ENROLL_STATES entering state 6 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Get check command 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.008: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.008: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.008: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Enroll check callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Response suffix valid: NO 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.008: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.008: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.008: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Device reported enroll completion 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: List 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] LIST_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Device fingerprint 1: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Number of currently enrolled fingerprints on the device is 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] LIST_STATES entering state 1 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Device reported listing completion 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] LIST_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Completing action FPI_DEVICE_ACTION_LIST in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-device-DEBUG: 00:01:23.009: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Enroll 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] ENROLL_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.009: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.009: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Device fingerprint 1: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Number of currently enrolled fingerprints on the device is 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] ENROLL_STATES entering state 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] ENROLL_STATES entering state 2 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] ENROLL_STATES entering state 3 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.010: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.010: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.011: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.011: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.011: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.011: [egismoc] ENROLL_STATES entering state 4 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.011: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.011: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.011: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.011: [egismoc] ENROLL_STATES entering state 5 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.011: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.011: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.011: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.011: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.012: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.012: [egismoc] ENROLL_STATES entering state 6 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Get check command 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.012: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.012: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.012: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Enroll check callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Response suffix valid: yes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.012: [egismoc] ENROLL_STATES entering state 7 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.012: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.012: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.012: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.013: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.013: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.013: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.013: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.013: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.013: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.013: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.013: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.013: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.013: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.013: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.013: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.013: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.013: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.013: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.013: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.014: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.014: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.014: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.014: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.014: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.014: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.014: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Partial capture successful. Please touch the sensor again (1/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.014: Device reported enroll progress, reported 1 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.014: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.014: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.014: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.015: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.015: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.015: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.015: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.015: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.015: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.015: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.015: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.015: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.015: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.015: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.015: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.015: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.015: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.016: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.016: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.016: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.016: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.016: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Partial capture successful. Please touch the sensor again (2/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.016: Device reported enroll progress, reported 2 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.016: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.016: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.016: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.016: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.017: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.017: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.017: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.017: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.017: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.017: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.017: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.017: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.017: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.017: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.017: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.017: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.017: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.018: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.018: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.018: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.018: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.018: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Partial capture successful. Please touch the sensor again (3/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.018: Device reported enroll progress, reported 3 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.018: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.018: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.018: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.018: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.019: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.019: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.019: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.020: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Partial capture successful. Please touch the sensor again (4/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.020: Device reported enroll progress, reported 4 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.020: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.020: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.020: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.020: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.020: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.020: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.020: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.021: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.021: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.021: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.021: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.021: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.021: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.021: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.021: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.021: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.021: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.021: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.021: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.021: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.022: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Partial capture successful. Please touch the sensor again (5/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.022: Device reported enroll progress, reported 5 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.022: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.022: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.022: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.022: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.022: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.022: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.022: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.022: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.023: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.023: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.023: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.023: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.023: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.023: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.023: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Partial capture successful. Please touch the sensor again (6/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.023: Device reported enroll progress, reported 6 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.023: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.023: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.023: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.024: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.024: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.024: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.024: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.024: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.024: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.024: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.024: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.024: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.024: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.024: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.024: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.024: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.024: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.025: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.025: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.025: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.025: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.025: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Partial capture successful. Please touch the sensor again (7/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.025: Device reported enroll progress, reported 7 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.025: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.025: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.025: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.025: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.026: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.026: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.026: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.026: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.026: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.026: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.026: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.026: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.026: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.026: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.026: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.027: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.027: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.027: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.027: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.027: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.027: Response suffix valid: NO 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.027: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.027: Response suffix valid: yes 191s (process:2571): libfprint-device-DEBUG: 00:01:23.027: Device reported enroll progress, reported 7 of 20 have been completed 191s listing - device should have prints 191s clear device storage 191s clear done 191s listing - device should be empty 191s enrolling 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 1, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 2, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 3, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 4, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 5, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 6, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 7, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 8, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 9, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 10, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 10, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 11, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 12, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 13, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 14, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 15, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 16, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 17, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 18, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 19, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 20, , None, None) 191s enroll done 191s listing - device should have 1 print 191s verifying 191s verify done 191s async identifying 191s indentification_done: 191s try to enroll duplicate 191s duplicate enroll attempt done 191s listing - device should still only have 1 print 191s enroll new finger 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 1, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 2, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 3, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 4, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 5, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 6, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 7, , None, None) 191s finger status: (process:2571): libfprint-SSM-DEBUG: 00:01:23.027: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.027: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.027: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.027: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.027: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.028: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.028: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.028: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.028: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.028: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.028: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.028: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.028: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.028: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.028: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.028: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.029: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.029: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Partial capture successful. Please touch the sensor again (8/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.029: Device reported enroll progress, reported 8 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.029: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.029: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.029: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.029: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.029: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.029: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.029: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.030: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.030: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.030: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.030: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.030: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.030: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.030: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.030: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.030: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.030: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.030: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.030: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.030: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.030: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.031: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Response suffix valid: NO 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Response suffix valid: yes 191s (process:2571): libfprint-device-DEBUG: 00:01:23.031: Device reported enroll progress, reported 8 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.031: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.031: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.031: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.031: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.031: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.031: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.031: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.032: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.032: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.032: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.032: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.032: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.032: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.032: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.032: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.032: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.032: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.032: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.032: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.032: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.032: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.033: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Partial capture successful. Please touch the sensor again (9/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.033: Device reported enroll progress, reported 9 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.033: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.033: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.033: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.033: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.033: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.033: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.033: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.033: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.034: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.034: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.034: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.034: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.034: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.034: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.034: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.034: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Partial capture successful. Please touch the sensor again (10/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.034: Device reported enroll progress, reported 10 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.034: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.034: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.034: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.035: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.035: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.035: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.035: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.035: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.035: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.035: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.035: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.035: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.035: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.035: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.035: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.035: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.035: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.035: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.036: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.036: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.036: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.036: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.036: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Partial capture successful. Please touch the sensor again (11/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.036: Device reported enroll progress, reported 11 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.036: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.036: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.036: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.036: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.037: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.037: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.037: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.037: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.037: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.037: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.037: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.037: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.037: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.037: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.037: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.038: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.038: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.038: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.038: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.038: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.038: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.038: Partial capture successful. Please touch the sensor again (12/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.038: Device reported enroll progress, reported 12 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.038: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.038: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.038: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.038: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.038: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.038: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.039: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.039: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.039: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.039: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.039: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.039: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.039: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.039: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.039: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.039: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.040: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.040: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Partial capture successful. Please touch the sensor again (13/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.040: Device reported enroll progress, reported 13 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.040: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.040: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.040: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.040: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.040: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.040: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.040: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.041: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.041: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.041: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.041: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.041: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.041: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.041: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.041: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.041: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.041: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.041: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.041: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.041: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.041: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.042: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Partial capture successful. Please touch the sensor again (14/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.042: Device reported enroll progress, reported 14 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.042: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.042: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.042: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.042: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.042: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.042: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.042: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.042: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.043: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.043: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.043: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.043: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.043: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.043: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.043: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Partial capture successful. Please touch the sensor again (15/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.043: Device reported enroll progress, reported 15 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.043: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.043: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.043: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.044: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.044: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.044: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.044: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.044: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.044: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.044: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.044: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.044: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.044: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.044: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.044: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.044: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.044: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.045: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.045: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.045: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.045: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.045: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Partial capture successful. Please touch the sensor again (16/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.045: Device reported enroll progress, reported 16 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.045: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.045: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.045: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.045: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.046: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.046: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.046: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.046: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.046: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.046: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.046: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.046: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.046: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.046: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.046: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.047: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.047: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Partial capture successful. Please touch the sensor again (17/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.047: Device reported enroll progress, reported 17 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.047: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.047: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.047: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.047: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.047: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.047: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.047: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.048: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.048: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.048: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.048: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.048: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.048: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.048: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.048: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.048: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.048: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.048: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.048: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.048: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.049: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.049: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.049: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.049: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.049: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.049: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.049: Partial capture successful. Please touch the sensor again (18/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.049: Device reported enroll progress, reported 18 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.049: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.049: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.049: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.049: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.049: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.050: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.050: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.050: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.050: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.050: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.050: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.050: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.050: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.051: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.051: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.051: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.051: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.051: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.051: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.051: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.051: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.051: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.051: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.051: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.051: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.051: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.052: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Partial capture successful. Please touch the sensor again (19/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.052: Device reported enroll progress, reported 19 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.052: [egismoc] ENROLL_STATES entering state 8 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.052: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.052: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.052: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.052: [egismoc] ENROLL_STATES entering state 9 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.052: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.052: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.053: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.053: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.053: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.053: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.053: [egismoc] ENROLL_STATES entering state 10 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.053: Wait for finger on sensor 191s (process:2571): libfprint-device-DEBUG: 00:01:23.053: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.053: Finger on sensor callback 191s (process:2571): libfprint-device-DEBUG: 00:01:23.053: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.053: [egismoc] ENROLL_STATES entering state 11 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.053: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.053: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.053: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.054: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.054: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.054: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.054: Read capture callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.054: Response prefix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.054: Response suffix valid: yes 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.054: Partial capture successful. Please touch the sensor again (20/20) 191s (process:2571): libfprint-device-DEBUG: 00:01:23.054: Device reported enroll progress, reported 20 of 20 have been completed 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.054: [egismoc] ENROLL_STATES entering state 12 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.054: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.054: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.054: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.054: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.055: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.055: [egismoc] ENROLL_STATES entering state 13 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: New fingerprint ID: FP1-00000000-7-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.055: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.055: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.055: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.055: [egismoc] ENROLL_STATES entering state 14 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.055: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.055: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.055: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Task SSM next state callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] ENROLL_STATES entering state 15 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Enrollment was successful! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.056: Device reported enroll completion 191s (process:2571): libfprint-device-DEBUG: 00:01:23.056: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2571): libfprint-device-DEBUG: 00:01:23.056: Print for finger FP_FINGER_RIGHT_INDEX enrolled 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] ENROLL_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.056: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.056: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: List 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] LIST_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Device fingerprint 1: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Device fingerprint 2: FP1-00000000-7-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Number of currently enrolled fingerprints on the device is 2 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] LIST_STATES entering state 1 191s (process:2571): libfprint-device-DEBUG: 00:01:23.056: Device reported listing completion 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] LIST_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.056: Completing action FPI_DEVICE_ACTION_LIST in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Delete 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] DELETE_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.056: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.056: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.057: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.057: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: Device fingerprint 1: FP1-00000000-2-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: Device fingerprint 2: FP1-00000000-7-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: Number of currently enrolled fingerprints on the device is 2 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.057: [egismoc] DELETE_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: Get delete command 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.057: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.057: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.057: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Delete callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Response prefix valid: yes 191s (process:2571): libfprint-device-DEBUG: 00:01:23.058: Device reported deletion completion 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] DELETE_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.058: Completing action FPI_DEVICE_ACTION_DELETE in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.058: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: List 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] LIST_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Device fingerprint 1: FP1-00000000-7-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Number of currently enrolled fingerprints on the device is 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] LIST_STATES entering state 1 191s (process:2571): libfprint-device-DEBUG: 00:01:23.058: Device reported listing completion 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] LIST_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.058: Completing action FPI_DEVICE_ACTION_LIST in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.058: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Clear storage 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] DELETE_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.058: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.058: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.059: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.059: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.059: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.059: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.059: Device fingerprint 1: FP1-00000000-7-00000000-nobody 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.059: Number of currently enrolled fingerprints on the device is 1 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.059: [egismoc] DELETE_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.059: Get delete command 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.059: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.059: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.059: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.059: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.060: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Delete callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Response prefix valid: yes 191s (process:2571): libfprint-device-DEBUG: 00:01:23.060: Device reported deletion completion 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.060: [egismoc] DELETE_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.060: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.060: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: List 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.060: [egismoc] LIST_STATES entering state 0 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Execute command and get response 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Get check bytes 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.060: [egismoc] CMD_STATES entering state 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.060: [egismoc] CMD_STATES entering state 1 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Command receive callback 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.060: [egismoc] CMD_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: List callback 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Number of currently enrolled fingerprints on the device is 0 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.060: [egismoc] LIST_STATES entering state 1 191s (process:2571): libfprint-device-DEBUG: 00:01:23.060: Device reported listing completion 191s (process:2571): libfprint-SSM-DEBUG: 00:01:23.060: [egismoc] LIST_STATES completed successfully 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Task SSM done 191s (process:2571): libfprint-device-DEBUG: 00:01:23.060: Completing action FPI_DEVICE_ACTION_LIST in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.060: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Closing device 191s (process:2571): libfprint-egismoc-DEBUG: 00:01:23.060: Cancel 191s (process:2571): libfprint-device-DEBUG: 00:01:23.061: Device reported close completion 191s (process:2571): libfprint-device-DEBUG: 00:01:23.061: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:2571): libfprint-device-DEBUG: 00:01:23.061: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 8, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 9, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 10, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 11, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 12, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 13, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 14, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 15, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 16, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 17, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 18, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 19, , None, None) 191s finger status: 191s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb590e3c0 (FpiDeviceEgisMoc at 0x3544950)>, 20, , None, None) 191s enroll new finger done 191s listing - device should have 2 prints 191s deleting first print 191s delete done 191s listing - device should only have second print 191s clear device storage 191s clear done 191s listing - device should be empty 191s ** (umockdev-run:2567): DEBUG: 00:01:23.074: umockdev.vala:154: Removing test bed /tmp/umockdev.WY2G22 191s (umockdev-run:2567): GLib-DEBUG: 00:01:23.076: unsetenv() is not thread-safe and should not be used after threads are created 191s Executing: libfprint-2/driver-egismoc-0587.test 191s PASS: libfprint-2/driver-egismoc-0587.test 191s Running test: libfprint-2/driver-synaptics.test 191s ** (umockdev-run:2579): DEBUG: 00:01:23.108: umockdev.vala:127: Created udev test bed /tmp/umockdev.VWG012 191s ** (umockdev-run:2579): DEBUG: 00:01:23.108: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 191s ** (umockdev-run:2579): DEBUG: 00:01:23.109: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 191s ** (umockdev-run:2579): DEBUG: 00:01:23.110: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.VWG012/dev/bus/usb/001/004 191s ** (umockdev-run:2579): DEBUG: 00:01:23.110: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 191s ** (umockdev-run:2579): DEBUG: 00:01:23.111: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 191s ** (umockdev-run:2579): DEBUG: 00:01:23.112: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.VWG012/dev/bus/usb/001/001 191s ** (umockdev-run:2579): DEBUG: 00:01:23.112: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 191s ** (umockdev-run:2579): DEBUG: 00:01:23.112: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 191s (process:2583): libfprint-context-DEBUG: 00:01:23.170: Initializing FpContext (libfprint version 1.94.8+tod1) 191s (process:2583): libfprint-tod-DEBUG: 00:01:23.170: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 191s (process:2583): libfprint-context-DEBUG: 00:01:23.171: No driver found for USB device 1D6B:0002 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.171: 76093201: ../libfprint/drivers/synaptics/synaptics.c:1243 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.172: Build Time: 1596608839 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.172: Build Num: 3273255 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.172: Version: 10.1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.172: Target: 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.172: Product: 65 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.172: sequence number is 1 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.172: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.172: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.173: Device reported probe completion 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.173: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 191s (process:2583): libfprint-device-DEBUG: 00:01:23.173: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.173: Not updating temperature model, device can run continuously! 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.174: 76095635: ../libfprint/drivers/synaptics/synaptics.c:1403 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.174: sequence number is 2 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.174: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.174: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.174: Device reported open completion 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.174: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 191s (process:2583): libfprint-device-DEBUG: 00:01:23.174: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.174: Not updating temperature model, device can run continuously! 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.174: clear all prints in database 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.174: sequence number is 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.174: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.175: Deleting All Enrolled Users is 0% complete 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.175: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.176: Deleting All Enrolled Users is 100% complete 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.176: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.176: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.176: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.176: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.176: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.176: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.176: Successfully deleted all enrolled user 191s (process:2583): libfprint-device-DEBUG: 00:01:23.176: Device reported deletion completion 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.176: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 191s (process:2583): libfprint-device-DEBUG: 00:01:23.176: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.176: Not updating temperature model, device can run continuously! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.177: Not updating temperature model, device can run continuously! 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.177: 76098626: ../libfprint/drivers/synaptics/synaptics.c:1014 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.177: user_id: FP1-00000000-0-00000000-nobody, finger: 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.177: sequence number is 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.177: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.177: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.177: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.177: Place Finger on the Sensor! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.177: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.178: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.178: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.178: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.178: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.178: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.178: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.178: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.178: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.179: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.179: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.179: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.180: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.180: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.180: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.181: Enrollment is 12 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.181: Device reported enroll progress, reported 1 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.181: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.181: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.181: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.181: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.182: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.182: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.182: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.183: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.183: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.183: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.184: Enrollment is 25 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.184: Device reported enroll progress, reported 2 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.184: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.184: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.184: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.184: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.184: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.184: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.184: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.184: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.184: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.184: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.185: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.185: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.185: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.186: Enrollment is 37 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.186: Device reported enroll progress, reported 3 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.186: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.187: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.187: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.187: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.187: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.187: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.187: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.187: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.187: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.188: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.188: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.188: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.188: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.188: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.188: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.188: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.188: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.188: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.188: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.189: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.189: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.189: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.189: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.190: Enrollment is 50 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.190: Device reported enroll progress, reported 4 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.190: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.191: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.191: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.191: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.191: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.191: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.191: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.191: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.191: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.192: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.192: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.192: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.192: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.192: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.192: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.192: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.192: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.192: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.192: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.193: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.193: Enrollment is 62 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.193: Device reported enroll progress, reported 5 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.193: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.194: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.194: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.194: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.194: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.195: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.195: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.195: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.195: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.196: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.196: Enrollment is 62 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.196: Device reported enroll progress, reported 5 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.196: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.197: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.197: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.197: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.198: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.198: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.199: Enrollment is 75 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.199: Device reported enroll progress, reported 6 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.199: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.199: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.199: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.199: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.200: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.200: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.200: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.200: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.200: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.200: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.200: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.200: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.200: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.200: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.200: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.201: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.201: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.202: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.202: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.202: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.202: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.202: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.202: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.202: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.202: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.202: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.202: Enrollment is 87 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.202: Device reported enroll progress, reported 7 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.202: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.203: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.203: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.203: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.203: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.204: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.204: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.204: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.204: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.204: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.204: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.204: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.205: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.205: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.205: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.205: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.206: Enrollment is 100 % 191s (process:2583): libfprint-device-DEBUG: 00:01:23.206: Device reported enroll progress, reported 8 of 8 have been completed 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.206: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.206: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.206: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.206: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.207: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.207: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.207: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.207: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.208: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.208: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.208: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.208: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.208: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.208: Enrollment was successful! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.208: Device reported enroll completion 191s (process:2583): libfprint-device-DEBUG: 00:01:23.208: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2583): libfprint-device-DEBUG: 00:01:23.208: Print for finger FP_FINGER_UNKNOWN enrolled 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.208: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 191s (process:2583): libfprint-device-DEBUG: 00:01:23.208: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.208: Not updating temperature model, device can run continuously! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.208: Not updating temperature model, device can run continuously! 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.208: data is 0x2ae00c0 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.208: 76130137: ../libfprint/drivers/synaptics/synaptics.c:646 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.208: sequence number is 5 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.208: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.208: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.209: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.209: Place Finger on the Sensor! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.209: got suspend request 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.209: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.209: got resume request 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.210: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.210: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.210: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.210: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.210: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.210: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.210: Finger is now on the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.210: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.210: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.210: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.210: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.211: Fingerprint image capture complete! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.211: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-device-DEBUG: 00:01:23.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.212: Finger is now off the sensor 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.212: Received message with 0 sequence number 0x91, ignoring! 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.212: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.212: interrupt transfer done 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.212: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.212: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.212: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.212: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.212: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 191s (process:2583): libfprint-device-DEBUG: 00:01:23.212: Device reported verify result 191s (process:2583): libfprint-device-DEBUG: 00:01:23.212: Device reported verify completion 191s (process:2583): libfprint-device-DEBUG: 00:01:23.212: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.212: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 191s (process:2583): libfprint-device-DEBUG: 00:01:23.212: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.212: Not updating temperature model, device can run continuously! 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.212: data is 0x2ae00c0 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.212: 76134374: ../libfprint/drivers/synaptics/synaptics.c:1123 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.212: sequence number is 6 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.212: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.213: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.213: Successfully deleted enrolled user 191s (process:2583): libfprint-device-DEBUG: 00:01:23.213: Device reported deletion completion 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.213: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 191s (process:2583): libfprint-device-DEBUG: 00:01:23.213: Completing action FPI_DEVICE_ACTION_DELETE in idle! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.213: Not updating temperature model, device can run continuously! 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.213: 76134901: ../libfprint/drivers/synaptics/synaptics.c:1424 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.213: sequence number is 7 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.213: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.213: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 191s (process:2583): libfprint-synaptics-DEBUG: 00:01:23.214: Fingerprint sensor ready to be powered down 191s (process:2583): libfprint-device-DEBUG: 00:01:23.214: Device reported close completion 191s (process:2583): libfprint-SSM-DEBUG: 00:01:23.214: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 191s (process:2583): libfprint-device-DEBUG: 00:01:23.214: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:2583): libfprint-device-DEBUG: 00:01:23.214: Not updating temperature model, device can run continuously! 191s enrolling 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 1, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 2, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 3, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 4, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 5, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 6, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 7, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbcb09d80 (FpiDeviceSynaptics at 0x27eb070)>, 8, None, None, None) 191s enroll done 191s verifying 191s verify done 191s deleting 191s delete done 191s libusb: warning [libusb_exit] device 1.1 still referenced 191s ** (umockdev-run:2579): DEBUG: 00:01:23.224: umockdev.vala:154: Removing test bed /tmp/umockdev.VWG012 191s (umockdev-run:2579): GLib-DEBUG: 00:01:23.226: unsetenv() is not thread-safe and should not be used after threads are created 191s PASS: libfprint-2/driver-synaptics.test 191s Running test: libfprint-2/driver-realtek-5816.test 191s ** (umockdev-run:2591): DEBUG: 00:01:23.257: umockdev.vala:127: Created udev test bed /tmp/umockdev.W3K312 191s ** (umockdev-run:2591): DEBUG: 00:01:23.257: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-6 191s ** (umockdev-run:2591): DEBUG: 00:01:23.259: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-6 (subsystem usb) 191s ** (umockdev-run:2591): DEBUG: 00:01:23.260: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.W3K312/dev/bus/usb/001/006 191s ** (umockdev-run:2591): DEBUG: 00:01:23.260: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 191s ** (umockdev-run:2591): DEBUG: 00:01:23.261: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 191s ** (umockdev-run:2591): DEBUG: 00:01:23.262: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.W3K312/dev/bus/usb/001/001 191s ** (umockdev-run:2591): DEBUG: 00:01:23.262: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 191s ** (umockdev-run:2591): DEBUG: 00:01:23.262: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 191s (process:2595): libfprint-context-DEBUG: 00:01:23.320: Initializing FpContext (libfprint version 1.94.8+tod1) 191s (process:2595): libfprint-tod-DEBUG: 00:01:23.321: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 191s (process:2595): libfprint-context-DEBUG: 00:01:23.322: No driver found for USB device 1D6B:0002 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.322: 76243709: ../libfprint/drivers/realtek/realtek.c:1225 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.323: Device name: Realtek USB2.0 Finger Print Bridge 191s (process:2595): libfprint-device-DEBUG: 00:01:23.323: Device reported probe completion 191s (process:2595): libfprint-device-DEBUG: 00:01:23.323: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.323: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.324: 76245779: ../libfprint/drivers/realtek/realtek.c:1270 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.324: [realtek] Init entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.324: [realtek] Init entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.324: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.325: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.325: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.325: [realtek] Init entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.325: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.325: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.325: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.325: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.326: [realtek] Init completed successfully 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.326: Init complete! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.326: Device reported open completion 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.326: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-device-DEBUG: 00:01:23.326: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.326: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.326: 76247545: ../libfprint/drivers/realtek/realtek.c:1333 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.326: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.326: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.326: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.326: Successfully cleared storage 191s (process:2595): libfprint-device-DEBUG: 00:01:23.326: Device reported deletion completion 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.326: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-device-DEBUG: 00:01:23.326: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.326: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.326: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.326: 76248396: ../libfprint/drivers/realtek/realtek.c:1202 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.326: [realtek] Enroll entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.326: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.327: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.327: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.327: [realtek] Enroll entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.327: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.328: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.328: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.329: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.329: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.329: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.329: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.329: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.329: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.329: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.330: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-device-DEBUG: 00:01:23.330: Device reported enroll progress, reported 1 of 8 have been completed 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.330: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.330: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.331: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.331: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.331: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.331: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.331: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.331: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.331: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.331: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-device-DEBUG: 00:01:23.331: Device reported enroll progress, reported 2 of 8 have been completed 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.331: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.332: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.332: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.333: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.333: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.333: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.333: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.333: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.333: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.333: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-device-DEBUG: 00:01:23.333: Device reported enroll progress, reported 3 of 8 have been completed 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.333: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.333: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.333: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.334: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.334: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.334: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.334: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.334: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.334: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.334: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.334: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.335: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.335: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.335: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.335: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.335: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.335: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.335: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-device-DEBUG: 00:01:23.335: Device reported enroll progress, reported 4 of 8 have been completed 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.335: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.335: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.335: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.336: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.336: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.337: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.337: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-device-DEBUG: 00:01:23.337: Device reported enroll progress, reported 5 of 8 have been completed 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.337: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.337: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.338: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.338: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.338: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.338: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.338: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.338: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.339: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.339: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.339: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.339: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.339: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.339: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-device-DEBUG: 00:01:23.339: Device reported enroll progress, reported 6 of 8 have been completed 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.339: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.339: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.340: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.340: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.340: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.341: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.341: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.341: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.341: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.341: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.341: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.341: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-device-DEBUG: 00:01:23.341: Device reported enroll progress, reported 7 of 8 have been completed 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.341: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.341: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.342: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.342: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.342: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.342: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.342: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.342: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.342: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.342: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.343: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.343: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.343: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.343: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.343: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.343: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.343: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-device-DEBUG: 00:01:23.343: Device reported enroll progress, reported 8 of 8 have been completed 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.343: [realtek] Enroll entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.343: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.344: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.344: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.344: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.344: [realtek] Enroll entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.344: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.344: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.344: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.344: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.345: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] Enroll entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.345: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] Enroll entering state 5 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.346: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.346: [realtek] Enroll entering state 6 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.346: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.346: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.346: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.346: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.346: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.347: [realtek] Enroll completed successfully 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.347: Enrollment complete! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.347: Device reported enroll completion 191s (process:2595): libfprint-device-DEBUG: 00:01:23.347: Print for finger FP_FINGER_UNKNOWN enrolled 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.347: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-device-DEBUG: 00:01:23.347: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.347: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.347: 76268629: ../libfprint/drivers/realtek/realtek.c:1345 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.347: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.347: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.347: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.348: Query templates complete! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.348: Device reported listing completion 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.348: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-device-DEBUG: 00:01:23.348: Completing action FPI_DEVICE_ACTION_LIST in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.348: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.348: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.348: 76269662: ../libfprint/drivers/realtek/realtek.c:1178 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.348: [realtek] Verify & Identify entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.348: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.348: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.348: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] Verify & Identify entering state 1 191s (process:2595): libfprint-device-DEBUG: 00:01:23.349: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] Verify & Identify entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.349: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.350: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.350: [realtek] Verify & Identify entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.350: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.350: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.350: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.350: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.350: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.350: [realtek] Verify & Identify entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.350: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.351: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.351: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.351: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.351: Device reported verify result 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.351: [realtek] Verify & Identify entering state 5 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.351: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.351: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.351: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.351: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.352: [realtek] Verify & Identify completed successfully 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.352: Verify complete! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.352: Device reported verify completion 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.352: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-device-DEBUG: 00:01:23.352: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.352: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.352: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.352: 76273810: ../libfprint/drivers/realtek/realtek.c:1178 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.352: [realtek] Verify & Identify entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.352: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.352: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.352: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] Verify & Identify entering state 1 191s (process:2595): libfprint-device-DEBUG: 00:01:23.353: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] Verify & Identify entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.354: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.354: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.354: [realtek] Verify & Identify entering state 3 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.354: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.354: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.354: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.354: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.355: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.355: [realtek] Verify & Identify entering state 4 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.355: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.355: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.355: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.355: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-device-DEBUG: 00:01:23.355: Device reported identify result 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.355: [realtek] Verify & Identify completed successfully 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.355: Verify complete! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.355: Device reported identify completion 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.355: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-device-DEBUG: 00:01:23.355: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.355: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.356: 76277482: ../libfprint/drivers/realtek/realtek.c:1314 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.356: [realtek] Delete print entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.356: [realtek] Delete print entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.357: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.357: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.357: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.357: [realtek] Delete print completed successfully 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.357: Delete print complete! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.357: Device reported deletion completion 191s (process:2595): libfprint-SSM-DEBUG: 00:01:23.357: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 191s (process:2595): libfprint-device-DEBUG: 00:01:23.357: Completing action FPI_DEVICE_ACTION_DELETE in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.357: Not updating temperature model, device can run continuously! 191s (process:2595): libfprint-realtek-DEBUG: 00:01:23.357: 76278712: ../libfprint/drivers/realtek/realtek.c:1302 191s (process:2595): libfprint-device-DEBUG: 00:01:23.357: Device reported close completion 191s (process:2595): libfprint-device-DEBUG: 00:01:23.357: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:2595): libfprint-device-DEBUG: 00:01:23.357: Not updating temperature model, device can run continuously! 191s enrolling 191s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb430a200 (FpiDeviceRealtek at 0x36e6150)>, 1, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb430a200 (FpiDeviceRealtek at 0x36e6150)>, 2, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb430a200 (FpiDeviceRealtek at 0x36e6150)>, 3, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb430a200 (FpiDeviceRealtek at 0x36e6150)>, 4, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb430a200 (FpiDeviceRealtek at 0x36e6150)>, 5, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb430a200 (FpiDeviceRealtek at 0x36e6150)>, 6, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb430a200 (FpiDeviceRealtek at 0x36e6150)>, 7, None, None, None) 191s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb430a200 (FpiDeviceRealtek at 0x36e6150)>, 8, None, None, None) 191s enroll done 191s listing 191s listing done 191s verifying 191s verify done 191s async identifying 191s indentification_done: 191s deleting 191s delete done 191s ** (umockdev-run:2591): DEBUG: 00:01:23.367: umockdev.vala:154: Removing test bed /tmp/umockdev.W3K312 191s (umockdev-run:2591): GLib-DEBUG: 00:01:23.370: unsetenv() is not thread-safe and should not be used after threads are created 191s PASS: libfprint-2/driver-realtek-5816.test 191s Running test: libfprint-2/driver-nb1010.test 191s ** (umockdev-run:2603): DEBUG: 00:01:23.401: umockdev.vala:127: Created udev test bed /tmp/umockdev.CIT912 191s ** (umockdev-run:2603): DEBUG: 00:01:23.401: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 191s ** (umockdev-run:2603): DEBUG: 00:01:23.405: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 191s ** (umockdev-run:2603): DEBUG: 00:01:23.406: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.CIT912/dev/bus/usb/001/003 191s ** (umockdev-run:2603): DEBUG: 00:01:23.406: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 191s ** (umockdev-run:2603): DEBUG: 00:01:23.410: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 191s ** (umockdev-run:2603): DEBUG: 00:01:23.411: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.CIT912/dev/bus/usb/001/001 191s ** (umockdev-run:2603): DEBUG: 00:01:23.411: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 191s ** (umockdev-run:2603): DEBUG: 00:01:23.413: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 191s ** (umockdev-run:2603): DEBUG: 00:01:23.414: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3 191s ** (umockdev-run:2603): DEBUG: 00:01:23.414: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 191s (umockdev-run:2603): GLib-GIO-DEBUG: 00:01:23.415: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 191s (process:2607): libfprint-context-DEBUG: 00:01:23.481: Initializing FpContext (libfprint version 1.94.8+tod1) 191s (process:2607): libfprint-tod-DEBUG: 00:01:23.481: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory 191s (process:2607): libfprint-context-DEBUG: 00:01:23.482: No driver found for USB device 1D6B:0002 191s (process:2607): libfprint-device-DEBUG: 00:01:23.482: Device reported probe completion 191s (process:2607): libfprint-device-DEBUG: 00:01:23.482: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s (process:2607): libfprint-device-DEBUG: 00:01:23.482: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.483: Image device open completed 191s (process:2607): libfprint-device-DEBUG: 00:01:23.483: Device reported open completion 191s (process:2607): libfprint-nb1010-DEBUG: 00:01:23.483: nb1010 Initialized 191s (process:2607): libfprint-device-DEBUG: 00:01:23.483: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:2607): libfprint-device-DEBUG: 00:01:23.483: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:2607): libfprint-device-DEBUG: 00:01:23.483: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.483: Activating image device 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.483: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.483: Image device activation completed 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.483: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.483: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 191s (process:2607): libfprint-SSM-DEBUG: 00:01:23.483: [nb1010] M_LOOP_NUM_STATES entering state 0 191s (process:2607): libfprint-device-DEBUG: 00:01:23.483: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:2607): libfprint-nb1010-DEBUG: 00:01:23.483: nb1010 Activated 191s (process:2607): libfprint-SSM-DEBUG: 00:01:23.533: [nb1010] M_LOOP_NUM_STATES entering state 1 191s (process:2607): libfprint-SSM-DEBUG: 00:01:23.533: [nb1010] M_LOOP_NUM_STATES entering state 2 191s (process:2607): libfprint-SSM-DEBUG: 00:01:23.534: [nb1010] M_LOOP_NUM_STATES entering state 3 191s (process:2607): libfprint-device-DEBUG: 00:01:23.534: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.534: Image device reported finger status: on 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.534: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 191s (process:2607): libfprint-SSM-DEBUG: 00:01:23.535: [nb1010] M_LOOP_NUM_STATES entering state 4 191s (process:2607): libfprint-SSM-DEBUG: 00:01:23.535: [nb1010] M_LOOP_NUM_STATES entering state 5 191s (process:2607): libfprint-SSM-DEBUG: 00:01:23.563: [nb1010] M_LOOP_NUM_STATES entering state 6 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.563: Image device captured an image 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.563: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 191s (process:2607): libfprint-device-DEBUG: 00:01:23.563: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:2607): libfprint-SSM-DEBUG: 00:01:23.563: [nb1010] M_LOOP_NUM_STATES completed successfully 191s (process:2607): libfprint-nb1010-DEBUG: 00:01:23.563: nb1010 ssm complete cb 191s (process:2607): libfprint-device-DEBUG: 00:01:23.563: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.563: Image device reported finger status: off 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.563: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.563: Deactivating image device 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.563: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.563: Image device deactivation completed 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.563: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 191s (process:2607): libfprint-nb1010-DEBUG: 00:01:23.563: nb1010 Deactivated 191s (process:2607): libfprint-image-DEBUG: 00:01:23.578: Minutiae scan completed in 0.014872 secs 191s (process:2607): libfprint-device-DEBUG: 00:01:23.578: Device reported capture completion 191s (process:2607): libfprint-device-DEBUG: 00:01:23.578: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 191s (process:2607): libfprint-device-DEBUG: 00:01:23.578: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s (process:2607): libfprint-image_device-DEBUG: 00:01:23.578: Image device close completed 191s (process:2607): libfprint-device-DEBUG: 00:01:23.578: Device reported close completion 191s (process:2607): libfprint-nb1010-DEBUG: 00:01:23.578: nb1010 Deinitialized 191s (process:2607): libfprint-device-DEBUG: 00:01:23.578: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:2607): libfprint-device-DEBUG: 00:01:23.578: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ** (umockdev-run:2603): DEBUG: 00:01:23.649: umockdev.vala:154: Removing test bed /tmp/umockdev.CIT912 191s (umockdev-run:2603): GLib-DEBUG: 00:01:23.652: unsetenv() is not thread-safe and should not be used after threads are created 191s Comparing PNGs /tmp/libfprint-umockdev-test-1vh1iauy/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 191s PASS: libfprint-2/driver-nb1010.test 191s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 191s (process:2614): libfprint-context-DEBUG: 00:01:23.676: Initializing FpContext (libfprint version 1.94.8+tod1) 191s (process:2614): libfprint-tod-DEBUG: 00:01:23.677: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 191s (process:2614): libfprint-tod-DEBUG: 00:01:23.677: Found TOD entry point symbol 0x3fface029d0, GType is 2929980411152 191s (process:2614): libfprint-tod-DEBUG: 00:01:23.677: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 191s (process:2614): libfprint-context-DEBUG: 00:01:23.677: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 191s (process:2614): libfprint-context-DEBUG: 00:01:23.677: created 191s (process:2614): libfprint-fake_test_dev_tod_current-DEBUG: 00:01:23.677: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 191s 191s (process:2614): libfprint-device-DEBUG: 00:01:23.677: Device reported probe completion 191s (process:2614): libfprint-device-DEBUG: 00:01:23.677: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s (process:2614): libfprint-device-DEBUG: 00:01:23.677: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:2614): GLib-DEBUG: 00:01:23.677: setenv()/putenv() are not thread-safe and should not be used after threads are created 191s TAP version 14 191s # random seed: R02S7dfbb98de5572b8f0f4d6d3b7b1372ab 191s 1..97 191s # Start of driver tests 191s ok 1 /driver/get_driver 191s ok 2 /driver/get_device_id 191s ok 3 /driver/get_name 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 4 /driver/is_open 191s ok 5 /driver/get_nr_enroll_stages 191s ok 6 /driver/set_nr_enroll_stages 191s ok 7 /driver/supports_identify 191s ok 8 /driver/supports_capture 191s ok 9 /driver/has_storage 191s ok 10 /driver/do_not_support_identify 191s ok 11 /driver/do_not_support_capture 191s ok 12 /driver/has_not_storage 191s ok 13 /driver/get_usb_device 191s ok 14 /driver/get_virtual_env 191s ok 15 /driver/get_driver_data 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 191s # 191s # libfprint-device-DEBUG: Device reported probe completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s ok 16 /driver/initial_features 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 191s # 191s # libfprint-device-DEBUG: Device reported probe completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 17 /driver/probe 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 18 /driver/open 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 19 /driver/close 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 191s # 191s # libfprint-device-DEBUG: Device reported enroll completion 191s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 20 /driver/enroll 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 191s # 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 21 /driver/verify 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 22 /driver/identify 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 191s # 191s # libfprint-device-DEBUG: Device reported capture completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 23 /driver/capture 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 191s # 191s # libfprint-device-DEBUG: Device reported listing completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 24 /driver/list 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 191s # 191s # libfprint-device-DEBUG: Device reported deletion completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 25 /driver/delete 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 191s # 191s # libfprint-device-DEBUG: Device reported deletion completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 26 /driver/clear_storage 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 191s # 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 191s # 191s # libfprint-device-DEBUG: Device reported deletion completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 27 /driver/cancel 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 191s # 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 191s # 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 191s # 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 191s # 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 28 /driver/critical 191s ok 29 /driver/get_current_action 191s ok 30 /driver/timeout 191s ok 31 /driver/error_types 191s ok 32 /driver/retry_error_types 191s # Start of get_scan_type tests 191s ok 33 /driver/get_scan_type/press 191s ok 34 /driver/get_scan_type/swipe 191s # End of get_scan_type tests 191s # Start of set_scan_type tests 191s ok 35 /driver/set_scan_type/press 191s ok 36 /driver/set_scan_type/swipe 191s # End of set_scan_type tests 191s # Start of finger_status tests 191s ok 37 /driver/finger_status/inactive 191s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s ok 38 /driver/finger_status/waiting 191s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s ok 39 /driver/finger_status/present 191s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 191s ok 40 /driver/finger_status/changes 191s # End of finger_status tests 191s # Start of features tests 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 191s # 191s # libfprint-device-DEBUG: Device reported probe completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 41 /driver/features/probe_updates 191s # End of features tests 191s # Start of initial_features tests 191s ok 42 /driver/initial_features/none 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s ok 43 /driver/initial_features/no_capture 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s ok 44 /driver/initial_features/no_verify 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s ok 45 /driver/initial_features/no_identify 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s ok 46 /driver/initial_features/no_storage 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s ok 47 /driver/initial_features/no_list 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s ok 48 /driver/initial_features/no_delete 191s ok 49 /driver/initial_features/no_clear 191s # End of initial_features tests 191s # Start of probe tests 191s # libfprint-device-DEBUG: Device reported probe completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 50 /driver/probe/error 191s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 191s # libfprint-device-DEBUG: Device reported probe completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 51 /driver/probe/action_error 191s # End of probe tests 191s # Start of open tests 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 52 /driver/open/error 191s # End of open tests 191s # Start of close tests 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 53 /driver/close/error 191s # End of close tests 191s # Start of enroll tests 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 191s # 191s # libfprint-device-DEBUG: Device reported enroll completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 54 /driver/enroll/error 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Device reported enroll progress, reported 1760910029 of 1616258769 have been completed 191s # libfprint-device-DEBUG: Device reported enroll progress, reported 1901696227 of 1616258769 have been completed 191s # libfprint-device-DEBUG: Device reported enroll progress, reported 1992443848 of 1616258769 have been completed 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 191s # 191s # libfprint-device-DEBUG: Device reported enroll completion 191s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 55 /driver/enroll/progress 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 191s # 191s # libfprint-device-DEBUG: Device reported enroll completion 191s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 56 /driver/enroll/update_nbis 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 57 /driver/enroll/update_nbis_wrong_device 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 58 /driver/enroll/update_nbis_wrong_driver 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 59 /driver/enroll/update_nbis_missing_feature 191s # Start of error tests 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Device reported enroll completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Device reported enroll completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Device reported enroll completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 60 /driver/enroll/error/no_print 191s # End of error tests 191s # End of enroll tests 191s # Start of verify tests 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 191s # 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 61 /driver/verify/fail 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 191s # 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 62 /driver/verify/retry 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 191s # 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 63 /driver/verify/error 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 64 /driver/verify/not_supported 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 65 /driver/verify/report_no_cb 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 66 /driver/verify/not_reported 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Device reported verify result 191s # libfprint-device-DEBUG: Device reported verify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 67 /driver/verify/complete_retry 191s # End of verify tests 191s # Start of identify tests 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 68 /driver/identify/fail 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 191s ok 69 /driver/identify/retry 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 191s ok 70 /driver/identify/error 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 191s ok 71 /driver/identify/not_reported 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 72 /driver/identify/complete_retry 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 73 /driver/identify/report_no_cb 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 74 /driver/identify/suspend_continues 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-device-DEBUG: Device reported identify result 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 75 /driver/identify/suspend_succeeds 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 191s # 191s # libfprint-device-DEBUG: Device reported identify completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s ok 76 /driver/identify/suspend_busy_error 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 191s # 191s # libfprint-device-DEBUG: Device reported close completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s ok 77 /driver/identify/suspend_while_idle 191s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 191s # libfprint-device-DEBUG: Tod version info is 'current' 191s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 191s # 191s # libfprint-device-DEBUG: Device reported open completion 191s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 191s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 193s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 193s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 193s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 193s # 193s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 193s # 193s # libfprint-device-DEBUG: Device reported identify completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 193s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 193s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 196s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 196s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 199s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 78 /driver/identify/warmup_cooldown 199s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 199s # End of identify tests 199s # Start of capture tests 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 79 /driver/capture/not_supported 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 199s # 199s # libfprint-device-DEBUG: Device reported capture completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s ok 80 /driver/capture/error 199s # End of capture tests 199s # Start of list tests 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 199s # 199s # libfprint-device-DEBUG: Device reported listing completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 81 /driver/list/error 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 82 /driver/list/no_storage 199s # End of list tests 199s # Start of delete tests 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 199s # 199s # libfprint-device-DEBUG: Device reported deletion completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 83 /driver/delete/error 199s # End of delete tests 199s # Start of clear_storage tests 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 199s # libfprint-device-DEBUG: Tod version info is 'current' 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 199s # 199s # libfprint-device-DEBUG: Device reported deletion completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 84 /driver/clear_storage/error 199s # End of clear_storage tests 199s # Start of cancel tests 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 199s # 199s # libfprint-device-DEBUG: Device reported deletion completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 85 /driver/cancel/fail 199s # End of cancel tests 199s # Start of get_current_action tests 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 86 /driver/get_current_action/open 199s # End of get_current_action tests 199s # Start of get_cancellable tests 199s ok 87 /driver/get_cancellable/error 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 88 /driver/get_cancellable/open 199s # Start of open tests 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 89 /driver/get_cancellable/open/internal 199s # End of open tests 199s # End of get_cancellable tests 199s # Start of action_is_cancelled tests 199s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 199s # libfprint-device-DEBUG: Tod version info is 'current' 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 90 /driver/action_is_cancelled/open 199s ok 91 /driver/action_is_cancelled/error 199s # Start of open tests 199s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 199s # libfprint-device-DEBUG: Tod version info is 'current' 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 92 /driver/action_is_cancelled/open/internal 199s # End of open tests 199s # End of action_is_cancelled tests 199s # Start of complete_action tests 199s # Start of all tests 199s ok 93 /driver/complete_action/all/error 199s # End of all tests 199s # End of complete_action tests 199s # Start of action_error tests 199s ok 94 /driver/action_error/error 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 199s # libfprint-device-DEBUG: Device reported enroll completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 199s # libfprint-device-DEBUG: Device reported verify completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 199s # libfprint-device-DEBUG: Device reported identify completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 199s # libfprint-device-DEBUG: Device reported capture completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 199s # libfprint-device-DEBUG: Device reported listing completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 199s # libfprint-device-DEBUG: Device reported deletion completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 199s # libfprint-device-DEBUG: Tod version info is 'current' 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 199s # libfprint-device-DEBUG: Device reported deletion completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s ok 95 /driver/action_error/all 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 199s # 199s # libfprint-device-DEBUG: Device reported enroll completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 199s # 199s # libfprint-device-DEBUG: Device reported verify completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 199s # 199s # libfprint-device-DEBUG: Device reported identify completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 199s # 199s # libfprint-device-DEBUG: Device reported capture completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 199s # 199s # libfprint-device-DEBUG: Device reported listing completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 199s # 199s # libfprint-device-DEBUG: Device reported deletion completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 199s # libfprint-device-DEBUG: Tod version info is 'current' 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 199s # 199s # libfprint-device-DEBUG: Device reported deletion completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s ok 96 /driver/action_error/fail 199s # End of action_error tests 199s # Start of timeout tests 199s ok 97 /driver/timeout/cancelled 199s # End of timeout tests 199s # End of driver tests 199s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 199s SUMMARY: total=25; passed=24; skipped=0; failed=1; user=12.0s; system=2.1s; maxrss=46156 199s FAIL: libfprint-2/fpi-assembling.test (Child process killed by signal 6) 199s /tmp/autopkgtest.DF7m5L/wrapper.sh: checking for leaked background processes... 199s /tmp/autopkgtest.DF7m5L/wrapper.sh: waiting for tee/cat subprocesses... 199s /tmp/autopkgtest.DF7m5L/wrapper.sh: cleaning up... 199s /tmp/autopkgtest.DF7m5L/wrapper.sh: Exit status: 2 199s autopkgtest: DBG: testbed command exited with code 2 199s autopkgtest [00:01:31]: test installed-tests: -----------------------] 199s autopkgtest: DBG: testbed executing test finished with exit status 2 199s autopkgtest: DBG: sending command to testbed: copyup /tmp/autopkgtest.DF7m5L/installed-tests-stdout /tmp/autopkgtest-work.5ogut_s7/out/installed-tests-stdout 200s autopkgtest: DBG: got reply from testbed: ok 200s autopkgtest: DBG: sending command to testbed: copyup /tmp/autopkgtest.DF7m5L/installed-tests-stderr /tmp/autopkgtest-work.5ogut_s7/out/installed-tests-stderr 200s autopkgtest: DBG: got reply from testbed: ok 200s installed-tests FAIL non-zero exit status 2 200s autopkgtest [00:01:32]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 200s autopkgtest: DBG: sending command to testbed: copyup /tmp/autopkgtest.DF7m5L/installed-tests-artifacts/ /tmp/autopkgtest-work.5ogut_s7/out/artifacts/ 200s autopkgtest: DBG: got reply from testbed: ok 200s autopkgtest: DBG: testbed command ['rm', '-rf', '/tmp/autopkgtest.DF7m5L/installed-tests-artifacts', '/tmp/autopkgtest.DF7m5L/autopkgtest_tmp'], kind short, sout raw, serr pipe, env [] 200s autopkgtest: DBG: testbed command exited with code 0 200s autopkgtest: DBG: needs_reset, previously=False, requested by run_tests() line 230 200s autopkgtest [00:01:32]: @@@@@@@@@@@@@@@@@@@@ summary 200s installed-tests FAIL non-zero exit status 2 200s autopkgtest: DBG: testbed stop 200s autopkgtest: DBG: testbed close, scratch=/tmp/autopkgtest.DF7m5L 200s autopkgtest: DBG: sending command to testbed: close 218s autopkgtest: DBG: got reply from testbed: ok 218s autopkgtest: DBG: sending command to testbed: quit 218s nova [W] Using flock in prodstack6-s390x 218s flock: timeout while waiting to get lock 218s Creating nova instance adt-plucky-s390x-libfprint-20250215-235811-juju-7f2275-prod-proposed-migration-environment-15-9222da39-3d71-44cd-acdf-2d32eb48f048 from image adt/ubuntu-plucky-s390x-server-20250215.img (UUID 099dc609-2061-4009-a65b-d554466baca0)... 218s nova [W] Timed out waiting for 59a964d1-9407-48fc-bbfb-9f224c4a65f7 to get deleted.